Include sent headers with CONNECT request to upstream proxy #6328
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.
Description
Includes the request headers from the client to the upstream proxy in the CONNECT request. Looking at #5802, and the relevant events, I don't believe that there is a way today to access the headers that are sent from the client and override the empty headers sent to the upstream proxy.
I don't know if this is the best way to tackle it, or if there is a reason to strip all the headers in the CONNECT request, but for my specific use case of the day, it would be nice to be able to handle the traffic differently based on the user agent of the caller.
Checklist