ResponseEmitter: Don't remove Content-Type and Content-Length when body is empty #2925
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
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.
Fixes #2924
I am not really sure what would be the best way to allow users to control behavior here and I think trying to guess whether user wants this behavior (like by checking against well known
X-Accel-Redirectheader orHEADmethod) is gonna end with unnecessary logic on our side as the list of conditions grows to accommodate different web servers and CDNs.I am also not sure whether we need to grow ResponseEmitter by such logic. Correct me if I'm wrong, but I believe this would only get into play if user specifically set
->withHeaderon empty body before, right?