<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Header values too restricted"
href="https://bugs.webkit.org/show_bug.cgi?id=167112#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Header values too restricted"
href="https://bugs.webkit.org/show_bug.cgi?id=167112">bug 167112</a>
from <span class="vcard"><a class="email" href="mailto:youennf@gmail.com" title="youenn fablet <youennf@gmail.com>"> <span class="fn">youenn fablet</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=167112#c1">comment #1</a>)
<span class="quote">> I'd like to have information here in the bug of what we are (too) strict
> about, what should be relaxed, and why. Thanks!</span >
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 <a href="https://fetch.spec.whatwg.org/#concept-header">https://fetch.spec.whatwg.org/#concept-header</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>