-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Agent handling of gzipped responses #7470
Merged
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why clone?
Why not use the Header built-in functions to handle removal?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clone
b/c I didn't think this Send function should mutate the caller's request object. If that's not an issue, then we can get rid of it.Is there a built-in to remove just a single value? https://golang.org/pkg/net/http/#Header.Del will delete all values for that header.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unless the request object is being used for some other purpose down the wire I think it's fine to mutate it. I would think once it gets to this point it won't be further modified and we don't log request headers (or if we do it's before this, I would expect).
I would assume you'd have the same problem with
deflate
or any other encoding so I imagine you should remove them all. You could first cache them if you wanted to then use it to decide how to respond to the client, which is not a bad option, since the client is telling the cache what it will accept. But in that case you'd probably want to cache them all, not remove gzip and then cache the rest.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
gzip
is a special case because the Go std library transparently adds it depending on headers being set. Nonetheless, I think it's probably fine to just unconditionally remove theAccept-Encoding
header on the request object. We're not giving up gzip to Vault since the agent's Transport will add it in anyway. I think caching can be deferred until we need to actually reprocess the response.