-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: http complete list of non-concat headers #3930
Conversation
The original test was only testing some of the headers that shouldn't be concatenated as per lib/_http_incoming.js, so now the full list is there. 'content-length` gives a parse error if you set it to a string, so the test for that header uses numbers.
// Test that certain response header fields do not repeat | ||
// Test that certain response header fields do not repeat. | ||
// 'content-length' should also be in this list, but it needs | ||
// a numeric header, so it's tested slightly differently. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be numeric value
?
LGTM with one tiny comment. CI: https://ci.nodejs.org/job/node-test-pull-request/797/ |
The original test was only testing some of the headers that shouldn't be concatenated as per lib/_http_incoming.js, so now the full list is there. 'content-length` gives a parse error if you set it to a string, so the test for that header uses numbers. PR-URL: #3930 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
CI was a little red, but not related to this. Made the comment fix when landing. Thanks! Landed in 174d4e4 |
The original test was only testing some of the headers that shouldn't be concatenated as per lib/_http_incoming.js, so now the full list is there. 'content-length` gives a parse error if you set it to a string, so the test for that header uses numbers. PR-URL: #3930 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
The file this commit changes came into master as a semver major change, as such it is not part of LTS. Removing the label |
The original test was only testing some of the headers that shouldn't be concatenated as per
lib/_http_incoming.js
, so now the full list is there and matches what's in the docs as well.content-length
gives aParseError
if you set it to a string, so the test for that header uses numbers.