Menu
HttpClient includes this as 'Keep-Alive' by default. I've been able to set it to 'Close' using httpClient.DefaultRequestHeaders.ConnectionClose = true; but how do I omit it altogether?
490
Therefore in HTTP 1.0 the client can tell the server that it will keep the connection open by using the connection: keep-alive header.
The Connection general header controls whether the network connection stays open after the current transaction finishes. If the value sent is keep-alive , the connection is persistent and not closed, allowing for subsequent requests to the same server to be done.
Adding User-Agent header to single HttpRequest If you wish to add the User-Agent header to a single HttpRequestMessage , this can be done like this: var httpClient = new HttpClient(); var request = new HttpRequestMessage(HttpMethod.
Use “KeepAlive On” to enable it. To disable, just use “KeepAlive Off”. It sets the maximum number of requests for every Keep-Alive connection. A value of 100 is normally good enough for almost any scenario.
I've seen this asked before and to my knowledge no one (not even the great Jon Skeet) has come up with a way to avoid sending the Connection header in the HttpClient or HttpWebRequest worlds without completely reinventing the wheel. It's happening somewhere very deep down in the weeds.
ConnectionClose is nullable, but setting it to null on both HttpClient.DefaultRequestHeaders AND HttpRequestMethod.Headers still results in a Connection: Keep-Alive header being sent.
To summarize:
HttpRequestHeaders.ConnectionClose = true => Connection: close
HttpRequestHeaders.ConnectionClose = false => Connection: Keep-Alive
HttpRequestHeaders.ConnectionClose = null => Connection: Keep-Alive
HttpWebRequest.KeepAlive = true => Connection: Keep-Alive
HttpWebRequest.KeepAlive = false => Connection: close
(HttpWebRequest.KeepAlive is not nullable)
153
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
