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: Fri, 14 Dec 2007 16:11:30 -0800
Message-ID: <47631BB2.1030800@sicking.cc>
To: Julian Reschke <julian.reschke@gmx.de>
CC: Anne van Kesteren <annevk@opera.com>, Maciej Stachowiak <mjs@apple.com>, Mark Baker <distobj@acm.org>, Boris Zbarsky <bzbarsky@mit.edu>, Bjoern Hoehrmann <derhoermi@gmx.net>, public-webapi@w3.org

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.

So if for no other reason, interoperability seems like a good argument 
for stating that this should be done.

/ Jonas
Received on Saturday, 15 December 2007 00:10:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:59 GMT