[PR #9368/02d8dba9 backport][3.10] Avoid using the proxy headers in the ConnectionKey if no proxy is in use #9378
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.
This is a backport of PR #9368 as merged into master (02d8dba).
What do these changes do?
Default proxy headers may be passed to the connector to be included in the event a proxy is being used. If no proxy is being used, we should not include the proxy auth and proxy headers in the
ConnectionKey
since it means we could end up creating a connection when one was already available for reuseAre there changes in behavior for the user?
no
Is it a substantial burden for the maintainers to support this?
no