<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#c10">Comment # 10</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: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=147445#c9">comment #9</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=147445#c8">comment #8</a>)
> > (In reply to <a href="show_bug.cgi?id=147445#c7">comment #7</a>)
> > > Understood, what this means is that those browsers adhere to an obsolete
> > > version of the HTTP spec here.
> > >
> > > Calling xhr.setRequestHeader(" ") is wrong on many levels, so I'm not
> > > willing to ask for a reversal of this spec change unless there is evidence
> > > that a sizable proportion of the internet is broken because of the change.
> >
> > As part of syncing WebKit and WPT tests, let's check this with W3C folks.
> > I filed <a href="https://critic.hoppipolla.co.uk/r/5681">https://critic.hoppipolla.co.uk/r/5681</a>
>
> Discussion link is: <a href="https://github.com/w3c/web-platform-tests/pull/2045">https://github.com/w3c/web-platform-tests/pull/2045</a></span >
Proposal seems to converge in trimming whitespace at XHR level.
That would mean sending an empty header value when passed value is " ".
IMHO, it makes sense when reading the RFC and is probably safer than throwing an exception, based on Chris feedback and what other browsers are doing...
ap, do you agree with that direction?</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>