[Webkit-unassigned] [Bug 147445] Validation in isValidHTTPHeaderValue is too sensitive.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Aug 4 06:37:26 PDT 2015


--- Comment #10 from youenn fablet <youennf at gmail.com> ---
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> > > 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 https://critic.hoppipolla.co.uk/r/5681
> Discussion link is: https://github.com/w3c/web-platform-tests/pull/2045

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?

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/20150804/a6bc87bb/attachment-0001.html>

More information about the webkit-unassigned mailing list