ENHANCEMENT - don't compress responses with the x-no-compression response header #7232
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.
I'm using an http-proxy to proxy to an endpoint intended for long polling. Now this endpoint writes a newline to the HTTP connection in regular intervals to make sure the connection stays alive.
The compression middleware however buffers the output produced by the endpoint (and the http-proxy) waiting for it to complete so it can compress it. This leads to the initiator closing the connection after not receiving back any data.
Having the proposed change in place lets me circumvent this problem by setting a header on the response object like this: