Repository navigation
Reuse upstream HTTP connections for Responses requests - #22
Closed
Ovler-Young wants to merge 1 commit into
Closed
Ovler-Young wants to merge 1 commit into
Ovler-Young wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Responses requests now reuse the upstream HTTP client for a given upstream URL, preserving connection pooling across requests. The client is replaced when the URL changes; authentication, provider selection, and session handling remain per request.
Validation:
cargo test --workspace --locked: 301 passed, 12 existing ignored.cargo fmtand scoped diff checks passed.