rdeago
commented
3 years ago Hello @gyorokpeter, thanks for using EmbedIO!
Your requirement being a blatant violation of the HTTP protocol, I strongly doubt you'll find any web server library supporting it out-of-the.-box, including EmbedIO. I don't think a "forced keep-alive" feature would make much sense, either.
That said, I understand that sometimes one has to work with what one is given. If you're willing to use a private fork of EmbedIO, here's how to force keep-alive with the least possibile modifications.
Just insert the following line of code below this line in src/EmbedIO/Net/Internal/HttpListenerRequest.cs (at the end of the FinishInitialization method):
Headers.Set("Connection", "keep-alive");As long as you use HttpListenerMode.EmbedIO, this will make EmbedIO treat all incoming requests as if they contained a Connection header with a value of keep-alive and act accordingly.
DISCLAIMERS
- I did not actually test the above code, although I'm pretty sure it works.
- As I said above, this is a blatant violation of the HTTP protocol, so do it at your own risk. If you break something, you own both (or all) pieces.
- EmbedIO will close a connection anyway if the response status code is one in a hard-coded list of values, and every 100 served requests anyway. The code that does this is here and is pretty easy to modify.
- Please keep your fork private; more specifically, do not distribute it under the name
EmbedIO. Intellectual property matters aside, someone could install your fork by mistake and then face some weird, hard-to-figure-out bug in production.
gyorokpeter
I would like to implement a web server that doesn't close connections, it should be up to the client to close them, even if the client doesn't explicitly specify "Connection: keep-alive" in the headers. This is because a client may send many requests and handling them in separate connections would be too much overhead. The clients are pre-existing applications which are known to support sending multiple requests through the same connection.