<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Validation in isValidHTTPHeaderValue is too sensitive."
href="https://bugs.webkit.org/show_bug.cgi?id=147445#c17">Comment # 17</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Validation in isValidHTTPHeaderValue is too sensitive."
href="https://bugs.webkit.org/show_bug.cgi?id=147445">bug 147445</a>
from <span class="vcard"><a class="email" href="mailto:ap@webkit.org" title="Alexey Proskuryakov <ap@webkit.org>"> <span class="fn">Alexey Proskuryakov</span></a>
</span></b>
<pre><span class="quote">> If we split the sub-issues, that would give:
> 1. Add support for trimming whitespaces in XHR.setRequestHeader</span >
I'm not sure if that would be an observable change in behavior given the below...
<span class="quote">> 2. Ensure XHR can set a header with an empty value</span >
I think that this should raise an exception.
<span class="quote">> 3. Ensure XHR can set "Content-Type" with an empty value</span >
Ditto.
<span class="quote">> 4. Decide what to do about empty values in the context of XHR combine rule.</span >
I remember that there was some discussion about which header field values to combine, and which to replace. We may even have a bugzilla bug.
This doesn't seem too important, as it would only affect authors who actively tried to shoot themselves in the foot by setting the same header multiple times, and expecting that to override the value.</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>