HTTP/1 parsing of responses without newlines after headers #27456
Conversation
wpt-pr-bot
requested review from
domfarolino,
jdm,
mnot,
youennf and
yutakahirano
| [ | ||
| "header: value\t", | ||
| "header: value ", | ||
| "header: value\f", |
There was a problem hiding this comment.
"" and "header: value\n" seems like the most important ones to test here.
Also seems worth testing "HTTP/1.1 200 OKAYISH" alone (no LF)
Per other comment, I'm concerned about large (HTTP-only) breakage from browsers actually enforcing this.
There was a problem hiding this comment.
I explicitly don't want to test header: value\n here as we do have interoperable behavior on not returning a network error there. Maybe that should change, but let's tackle that separately.
There was a problem hiding this comment.
Are you sure? I'm pretty sure Chrome doesn't allow that over HTTPS.
There was a problem hiding this comment.
I guess I should create separate HTTPS tests then...
|
Was just looking through PRs that were assigned to me on GitHub and came across this. What's the status? |
|
As per above, this needs an HTTPS test. It might also need some reevaluation of the results across implementations given the time that has passed. |
For whatwg/fetch#472.