Ole Christian Eidheim

@Lucas-W No chunked transfer would have to be implemented by you on top of Simple-Web-Server. See the default_resource example on how to send a file piece by piece. One could...

@yangruixuan This is due to the `form` attribute `enctype="multipart/form-data"` (you can read more about this in https://tools.ietf.org/html/rfc7578). You would have to decode this yourself at the moment. Not sure if...

Accepting posted file(s) from a web browser was a bit more complex than I initially thought. This is due to the strange `multipart/form-data` that needs to be supported. Why this...

Regarding registering handlers once to run both HTTP and HTTPS: I think maybe you can write a resource function and copy it to both a HTTP resource and HTTPS resource...

I'm no help on Windows, but these systems sounds pretty old. At some point, there will be systems that we cannot support, sorry.

Aha, so this is a warning since cancel with error code is deprecated. I'll have to look into all the changes that has been made, and other deprecations that have...

Deprecation of https://www.boost.org/doc/libs/1_67_0/doc/html/boost_asio/reference/basic_waitable_timer/cancel/overload2.html seems like an error to me though, since this is not deprecated: https://www.boost.org/doc/libs/1_67_0/doc/html/boost_asio/reference/basic_stream_socket/cancel/overload2.html

Thank you for reporting these issue. Especially the case when the server is using port 0 has to be fixed. Regarding your second issue, here is a sample showing how...

Since parsing of a HTTP path variables is outside of the scope of this project, you would have to implement this yourself. You could use `^/search?(.*)$` as regex and parse...

1. Please see [Simple-WebSocket-Server](https://github.com/eidheim/Simple-WebSocket-Server). The WebSocket implementation is quite different from a Web Server implementation, so I decided to keep the projects separate. 2. Your task here sounds like it...