Always request querier to return gzipped response #4960
Merged
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.
What this PR does:
Before this change, the query-frontend did not do any manipulation for instant queries and the QF was basically a proxy.
#4863 changed that and introduced middlewares also for instant queries in order to be able to manipulate the queries and implement the
shard by
optimization.The problem now is that we are not forwarding all the headers from the original request to the querier, including the
Accept-Encoding
one and, this means that we stopped to gzip those requests between the query-frontend and the querier.PS: This was already the case for
query_range
This PR is changing this behavior and making the QF always ask the querier to return the response gzipped.
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]