[Webkit-unassigned] [Bug 167112] Header values too restricted

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jan 17 17:45:43 PST 2017


--- Comment #2 from youenn fablet <youennf at gmail.com> ---
(In reply to comment #1)
> I'd like to have information here in the bug of what we are (too) strict
> about, what should be relaxed, and why. Thanks!

I introduced a while back enforcement of the ABNF for header values.
This is now obsolete and no other browser is implementing it.
Fetch API is temporarily defining validation rules for header values.
I guess that once HTTPBis WG will carry on the changes to the corresponding RFC, fetch spec will just refer to it.

The restriction I added is roughly that all characters below 0x20 (except for tab) would lead to make a header value invalid.

The proposed validation rule is defined in https://fetch.spec.whatwg.org/#concept-header

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170118/84be44d2/attachment-0001.html>

More information about the webkit-unassigned mailing list