| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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.
There was a problem hiding this comment.
Should this be numeric value?
Sorry, something went wrong.
|
LGTM with one tiny comment. CI: https://ci.nodejs.org/job/node-test-pull-request/797/ |
Sorry, something went wrong.
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 |
Sorry, something went wrong.
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 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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 a ParseError if you set it to a string, so the test for that header uses numbers.