- From: Ian Hickson <ian@hixie.ch>
- Date: Mon, 22 Oct 2012 22:39:01 +0000 (UTC)
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- cc: Bobby Holley <bobbyholley@gmail.com>, Adam Barth <w3c@adambarth.com>, public-script-coord@w3.org
On Mon, 22 Oct 2012, Boris Zbarsky wrote: > On 10/22/12 5:31 PM, Ian Hickson wrote: > > The HTTP header should be set as defined here: > > > > http://www.whatwg.org/specs/web-apps/current-work/#fetch > > > > Is this not sufficiently well defined? > > It's well defined. The current definition matches Gecko and WebKit, but not > Trident and Presto. > > Gecko would like to change its behavior to that of Trident and Presto, and > we're suggesting that the spec should change to align with the now-majority > behavior. But we're trying to see whether WebKit would be willing to change > as well, before doing that. > > This was all covered in the mail that started this thread, and I thought it > was covered clearly. Again, see > http://lists.w3.org/Archives/Public/public-script-coord/2012OctDec/0014.html I'm confused. The cited document is talking about the DOM API, not the HTTP header. But earlier you said this was about the HTTP header, not the API. The text quoted in the cited document has nothing to do with what is sent over HTTP. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 22 October 2012 22:39:23 UTC