Fix content-length calcuation in Rack:Response#write #2150
Merged
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.
When
Rack::Response
is initialized with an Array, it properly sets its internal@length
value and emitted content-length header on the first use ofwrite
. But every subsequent timewrite
is called, it increments the length incorrectly, resulting in an incorrect content-length header.This commit fixes the accumulation bug, and fixes/adds specs to properly test the scenario where
write
is used multiple times.Fixes #2148