Question

Does a HttpContext always have only one HttpConnection? When I execute a request, does it maintain only one HttpConnection even though there may be multiple socket connections due to redirects etc.?

Was it helpful?

Solution

HttpContext always refers to the current or the last connection used by the HTTP exchange regardless of how many intermediate connection may have been employed in the course of the exchange. Connection re-use and pooling is a responsibility of the connection manager.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top