Skip to content

Conversation

@kanongil
Copy link
Contributor

The transmit logic incorrectly considers missing content-length headers as having a payload length of 0, while it usually signals that chunked transfer encoding should be used (with any actual length).

This patch fixes this by always parsing the header value, and testing using integer comparisons instead of the current truthiness tests.

I have added 2 new tests to verify the chunked response behavior. I also fixed an existing compression test, which was actually not working as intended due to not signalling a compressible mime type.

@kanongil
Copy link
Contributor Author

Note that this bug actually causes incorrect responses when chunked transfers are used along with response.emptyStatusCode === 204.

@hueniverse hueniverse added the bug Bug or defect label Oct 23, 2015
@hueniverse hueniverse added this to the 11.0.3 milestone Oct 23, 2015
@hueniverse hueniverse self-assigned this Oct 23, 2015
hueniverse added a commit that referenced this pull request Oct 23, 2015
Fix empty content-length handling for gzip and 204 responses
@hueniverse hueniverse merged commit 8ca9333 into hapijs:master Oct 23, 2015
@lock
Copy link

lock bot commented Jan 9, 2020

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

bug Bug or defect

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants