Repository navigation
Conversation
|
Review requested:
|
|
There's merge conflicts here. I think to go forward this should align with #63571 (just about to merge right now). We'd want a matching I think the path validation is correct as-is, but for header values this PR rejects control codes like 0x01–0x08 while browser fetch does allow those: WHATWG excludes only >0xff, 0x0, and newlines (https://fetch.spec.whatwg.org/#header-value). Totally on board with the goal here, it would be good to follow the HTTP RFCs strictly by default for Node in general, as long as we keep the door open for that relaxed behaviour for fetch use cases. For HTTP/2 we already have a related option: |
The linked PR is this PR. Which one you meant? |
|
😂 ah sorry! I meant #61597 |
… option Signed-off-by: Matteo Collina <hello@matteocollina.com> PR-URL: nodejs#63571
db6b9a4 to
1af0980
Compare
2446dce to
2a31214
Compare
- Disable strictFieldWhitespaceValidation in relaxed/insecure mode so it does not conflict with the relaxed behaviour (per @pimterry review). - Document that relaxed/insecure subsumes strictSingleValueFields and strictFieldWhitespaceValidation. - Add integration tests for the http2.connect() httpValidation option.
2a31214 to
cfef7fb
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #63571 +/- ##
==========================================
- Coverage 90.69% 90.69% -0.01%
==========================================
Files 797 801 +4
Lines 279611 281905 +2294
Branches 53787 54329 +542
==========================================
+ Hits 253603 255676 +2073
- Misses 16295 16363 +68
- Partials 9713 9866 +153
🚀 New features to boost your workflow:
|
The http2 client request headers array form is a flat list of [name, value, name, value, ...], not an array of pairs.
:pathpseudo-header