Fix duplicate Transfer-Encoding: chunked on HTTP/1.1 responses#616
Merged
Conversation
Header.ForceTransferChunked() unconditionally appended a Transfer-Encoding: chunked header, producing a duplicate when the upstream HTTP/1.1 response already carried one. Strict clients (Go net/http) reject such responses. Make the method idempotent by returning early when ChunkedBody is already true.
This was referenced Apr 13, 2026
This file contains hidden or 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
1 participant
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.
Summary
Header.ForceTransferChunked()unconditionally appended aTransfer-Encoding: chunkedheader, producing a duplicate when the upstream HTTP/1.1 response already carried one. Strict clients such as Gonet/httpreject the response withtoo many transfer encodings: ["chunked" "chunked"].ForceTransferChunked()idempotent by returning early whenChunkedBodyis already true. The guard lives inHeaderrather than at the call site inProxyOrchestratorso all current and future callers are protected.https://noaa-goes16.s3.amazonaws.com/(the origin reported in the issue) withForceHttp11Actionpinning the upstream leg to HTTP/1.1.Refs #615