x/website: update 1.16 release notes to indicate that ReverseProxy no longer changes transfer-encoding: chunked to content-length for small responses #48996
Labels
FrozenDueToAge
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
website
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Transfer-Encoding: chunked
See example in playground: https://play.golang.org/p/pRkFwyre5Bt.
What did you expect to see?
Prior to golang 1.16.0, the response would contain the
Content-Length
header.What did you see instead?
Since golang 1.16.0, the response contains the
Transfer-Encoding: chunked
header.I was able to use git bisect to narrow it down to this commit that changed things.
This change broke some of our clients and it would be nice to call it out in the release notes.
Current Release Note
ReverseProxy now flushes buffered data more aggressively when proxying streamed responses with unknown body lengths.
Link to release note
Proposed Release Note
ReverseProxy now flushes buffered data more aggressively when proxying streamed responses with unknown body lengths. Because of this, when a backend sends a small response with the
Transfer-Encoding: chunked
header, this header is no longer replaced with theContent-Length
header.Sending a CL momentarily.
The text was updated successfully, but these errors were encountered: