W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

Re: [CORS] HTTP error codes in preflight response

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 21 Sep 2010 11:04:33 +0200
To: "Webapps WG" <public-webapps@w3.org>, "Jonas Sicking" <jonas@sicking.cc>
Message-ID: <op.vjdktuwr64w2qv@anne-van-kesterens-macbook-pro.local>
On Tue, 21 Sep 2010 02:05:10 +0200, Jonas Sicking <jonas@sicking.cc> wrote:
> CORS was recently clarified to say that error responses, such as
> 4xx/5xx responses, should not abort the various algorithms but instead
> such a response should be forwarded to, for example, the
> XMLHttpRequest implementation.
>
> However it seems somewhat strange to me to do this with responses to
> the preflight OPTIONS request. If a OPTIONS request results in a 404,
> then it seems to me that the request can not be considered successful,
> and that access to place the "real" request should not be granted.
> Otherwise we are essentially ignoring the status code and not exposing
> it anywhere, which seems strange.

So preflight requests should only succeed if the status code of the  
response is 200, correct? All other status codes mean failure? (Not  
counting 1xx here, as they are transport codes, not response codes.)


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Tuesday, 21 September 2010 09:05:15 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:40 GMT