Reputation: 279
I'm using a custom HTTP/1.1 client to connect to my apache server through HTTPS. This client requires the connection to be kept alive for at least 2 HTTP requests. However, I noticed that when using HTTPS, the web server will close the TLS connection after only one HTTP request even though keep-alive should be the default for HTTP/1.1 (when connecting to the same server through HTTP, the connection will be kept alive).
The concrete error that the client encounters is that the Windows API handling the secure connection will return SEC_I_CONTEXT_EXPIRED
indicating that the remote server initiated a shutdown.
How can I prevent this behaviour?
Upvotes: 0
Views: 147