<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#c14">Comment # 14</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#c13">comment #13</a>)
<span class="quote">> I think that it's a misunderstanding. Setting an empty Content-Type results
> in a malformed header field value with CFNetwork (tested on OS X 10.9.5):
>
> Content-Type: , application/xml
>
> So, trimming spaces wouldn't help.</span >
Ah I see...
HTTP allows empty header values AFAIK. HPack supports it also.
Is it considered as a CFNetwork bug? Is it envisioned to update CFNetwork?
If we think CFNetwork will have support for it in the future, we should keep the idea of trimming whitespaces at XHR level and try to find a temporary solution.
<span class="quote">> And sorry for sounding like a broken record, but removing Content-Type is a
> bad idea, I don't see any reason to make that possible through
> XMLHttpRequest.</span >
Agreed.</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>