Correctly dispose objects to release HTTP connections #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During live usage I discovered the maximum HTTP connections (defaults to 2) were excused, as a result the application hung on the third request. The fix is to correctly dispose of the HTTP request/response objects, something I thought unnecessary for HttpClient.
👍 to @robcthegeek, who resolutely disposed of the request/response objects when we worked together on another project 😄