-
-
Notifications
You must be signed in to change notification settings - Fork 34.7k
http: align header value validation with Fetch spec #61597
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
Open
RajeshKumar11
wants to merge
3
commits into
nodejs:main
Choose a base branch
from
RajeshKumar11:fix/http-header-value-validation-61582
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+116
−24
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -256,17 +256,31 @@ | |
| return true; | ||
| } | ||
|
|
||
| const headerCharRegex = /[^\t\x20-\x7e\x80-\xff]/; | ||
| // Strict header value regex per RFC 7230 (original/default behavior): | ||
| // field-value = *( field-content / obs-fold ) | ||
| // field-content = field-vchar [ 1*( SP / HTAB ) field-vchar ] | ||
| // field-vchar = VCHAR / obs-text | ||
| // This rejects control characters (0x00-0x1f except HTAB) and DEL (0x7f). | ||
| const strictHeaderCharRegex = /[^\t\x20-\x7e\x80-\xff]/; | ||
|
|
||
| // Lenient header value regex per Fetch spec (https://fetch.spec.whatwg.org/#header-value): | ||
| // - Must contain no 0x00 (NUL) or HTTP newline bytes (0x0a LF, 0x0d CR) | ||
| // - Must be byte sequences (0x00-0xff), not arbitrary unicode | ||
| // This allows most control characters except NUL, CR, and LF. | ||
| // eslint-disable-next-line no-control-regex | ||
| const lenientHeaderCharRegex = /[\x00\x0a\x0d]|[^\x00-\xff]/; | ||
|
|
||
| /** | ||
| * True if val contains an invalid field-vchar | ||
| * field-value = *( field-content / obs-fold ) | ||
| * field-content = field-vchar [ 1*( SP / HTAB ) field-vchar ] | ||
| * field-vchar = VCHAR / obs-text | ||
| * True if val contains an invalid header value character. | ||
| * By default uses strict validation per RFC 7230. | ||
| * When lenient=true, uses relaxed validation per Fetch spec. | ||
| * @param {string} val | ||
| * @param {boolean} [lenient=false] - Use lenient validation (Fetch spec rules) | ||
|
Check failure on line 278 in lib/_http_common.js
|
||
| * @returns {boolean} | ||
| */ | ||
| function checkInvalidHeaderChar(val) { | ||
| return headerCharRegex.test(val); | ||
| function checkInvalidHeaderChar(val, lenient = false) { | ||
| const regex = lenient ? lenientHeaderCharRegex : strictHeaderCharRegex; | ||
| return regex.test(val); | ||
| } | ||
|
|
||
| function cleanParser(parser) { | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
Nit: the comment should clarify that this is the original behavior