Frank Hessel

Hi Lothar, **First: Using the code in esp-idf** I only have experience in programming the ESP32 using the Arduino layer on top of the esp-idf, so I have a bit...

I split this ticket apart, so the web socket part can now be discussed/tracked under issue #13.

At the moment that's not possible, as the handler function would need to tell the server that the request is only processed partially. I assume that it's possible, but it...

Yes your are right. By "in state `HEADERS_FINISHED`" I meant to do it at the beginning of that state. Checking for the websocket handshake at the end of `STATE_REQUEST_FINISHED` should...

I think that's a feasible way to implement the web sockets initially, but on long term I would make the task separation optional or let the library user do it,...

I'm currently implementing support for middleware functions (see #10) because I need them for one project I'm working on. The way I do it is to use the `functional` part...

That was a part I changed for #17, because there are differences in the API for checking if there are input bytes remaining depending of the protocol you use (plain...

I added the call to SSL_pending() again. Furthermore, if you run into size limits while parsing the headers, have a look at `HTTPSServerConstants.hpp`, especially at the `HTTPS_REQUEST_MAX...` definitions. You can...

The examples in the repository only include a very basic code for the wifi handling, to focus on the server itself. So the connection is made once, but not restored...

It's maybe a naming issue, as there's no official name for the URL wildcards. Within the library, the following convention should be used consistently: _URL parameters_ name those wildcard parts...