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

(wrong string) €™t explain what to do when method is GET

From: Maciej Stachowiak <mjs@apple.com>
Date: Sat, 15 Dec 2007 13:36:45 -0800
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
Message-Id: <4620FE02-21D0-42EB-BD12-246625FF9ADA@apple.com>
To: Jonas Sicking <jonas@sicking.cc>


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, Bjrn already reported that both IE7 and FF happily  
>> pass the body, as they should (IMHO).
>
> My reading of Bjrns 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?)

Regards,
Maciej
Received on Saturday, 15 December 2007 21:37:02 GMT

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