-
-
Notifications
You must be signed in to change notification settings - Fork 37.1k
Missing second space in status line not rejected #62193
Copy link
Copy link
Closed as not planned
nodejs/llhttp
#869Closed as not planned
Copy link
Labels
http_parserIssues and PRs related to the HTTP parser implementation or http_parser binding.Issues and PRs related to the HTTP parser implementation or http_parser binding.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Description
Activity
Metadata
Metadata
Assignees
Labels
http_parserIssues and PRs related to the HTTP parser implementation or http_parser binding.Issues and PRs related to the HTTP parser implementation or http_parser binding.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Version
v25.7.0
Platform
Subsystem
HTTP
What steps will reproduce the bug?
Make an HTTP request to a server that replies with a status line such as
HTTP/1.1 200(note the lack of trailing space).How often does it reproduce? Is there a required condition?
100%
What is the expected behavior? Why is that the expected behavior?
Per RFC9112 §4.9:
So this is not a valid response and should be rejected.
What do you see instead?
Parsed correctly.
Additional information
Node.js’s parser is extremely strict, so this surprised me.