feat(config): Add an option for upstream content encoding #771
Conversation
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
tonyo
approved these changes
Sep 11, 2020
jan-auer
added a commit
that referenced
this pull request
Sep 16, 2020
* master: release: 20.9.0 ci(craft): Remove gh-pages target (#776) release: 0.7.0 ref(cabi): Remove unused scrub_event function (#773) fix(server): Disable generic network error handling (#772) feat(auth): Add version info for analytics (#758) feat(config): Add an option for upstream content encoding (#771) fix(server): Assign a default name for unnamed attachments (#769)
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.
Adds the
http.encodingconfiguration option to disable or change compression of upstream store requests. It is planned that this is eventually applied to all upstream requests, hence the generic naming.By default, compression should be enabled by all Relays. Sentry applies more aggressive limits on the content-length of raw requests than after decompression. However, in the current state, compression can become a bottleneck in high throughput scenarios, in which case it may be more beneficial to disable compression.