-
Notifications
You must be signed in to change notification settings - Fork 325
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
HTTP/2 headers #1316
Labels
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I played around a bit with WPT's H2 support and I found that Chrome is quite restrictive on header values, unless I'm missing something. Basically, if they contain (after stripping leading and trailing HTTP whitespace, which includes newlines) anything but:
there's a network error.
This is for responses. I haven't checked requests (the API allows 0x80 and friends).
Firefox is a lot more permissive.
Restricting this seems reasonable, though we cannot really change the API (should there be an opt-in? probably not) or HTTP/1 behavior. If HTTP/2 (and HTTP/3?) do not require this already then perhaps Fetch should. At the very least it seems worth mentioning around the definition of header value.
The text was updated successfully, but these errors were encountered: