You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 27, 2020. It is now read-only.
As described in this article, https://aspnetmonsters.com/2016/08/2016-08-27-httpclientwrong/, an application should limit the number HttpClient objects that are created and reuse it for subsequent requests. Otherwise it would open a new TCP connection for each request and it would be very easy to hit an application pools max queue length of 1000 for any website using this code as is.
The sample code in the readme should add a disclaimer describing the issue or be updated to a more complete implementation.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As described in this article, https://aspnetmonsters.com/2016/08/2016-08-27-httpclientwrong/, an application should limit the number HttpClient objects that are created and reuse it for subsequent requests. Otherwise it would open a new TCP connection for each request and it would be very easy to hit an application pools max queue length of 1000 for any website using this code as is.
The sample code in the readme should add a disclaimer describing the issue or be updated to a more complete implementation.
The text was updated successfully, but these errors were encountered: