W3C home > Mailing lists > Public > public-webapi@w3.org > December 2007

Re: [XHR] send doesn’t explain what to do when method is GET

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 17 Dec 2007 17:44:43 -0800
Message-ID: <4767260B.4050808@sicking.cc>
To: Maciej Stachowiak <mjs@apple.com>
CC: Julian Reschke <julian.reschke@gmx.de>, Anne van Kesteren <annevk@opera.com>, Mark Baker <distobj@acm.org>, Boris Zbarsky <bzbarsky@mit.edu>, Bjoern Hoehrmann <derhoermi@gmx.net>, public-webapi@w3.org

Maciej Stachowiak wrote:
> On Dec 14, 2007, at 4:11 PM, Jonas Sicking wrote:
>> Julian Reschke wrote:
>>> Jonas Sicking wrote:
>>>> Does any currently released browse include the body when doing an 
>>>> XHR GET request? If a big majority of them currently drop the body, 
>>>> then it seems like it would help interoperability if the spec 
>>>> explicitly stated that the body should be dropped.
>>> Disagreed. Please do not try to standardize HTTP APIs that profile 
>>> what HTTP allows.
>> XHR already disallows a lot of things that HTTP allows. Setting 
>> certain headers, cross site requests, etc. Why is this different?
>>> Besides that, Björn already reported that both IE7 and FF happily 
>>> pass the body, as they should (IMHO).
>> My reading of Björns email was that they did not drop it for HEAD, 
>> OPTIONS and EXAMPLE did not drop the entity body. In my testing IE, 
>> Firefox and Opera all dropped the entity body of GET requests.
> Did you try Safari (or can you post the test case so I can try it?)

I did not try safari. You can try it here:


/ Jonas
Received on Tuesday, 18 December 2007 01:44:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:24 UTC