W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: [cors] when a preflight goes bad

From: Benson Margulies <bimargulies@gmail.com>
Date: Mon, 5 Dec 2011 10:57:17 -0500
Message-ID: <CALhtWkfJrsao6HwO-YBiq1EAJfWPyY6_ABTUberiLhnUpHfKLA@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: public-webapps@w3.org, Sergey Beryozkin <sberyozkin@gmail.com>
>> The spec for resource sharing never discusses a status code for a
>> failed. It just says, 'terminate'.
>> To me, this suggests that, if there is no other OPTIONS processing
>> going on, the net result will be a NOT FOUND.
>> For that matter, it occurs to me, even if the entire preflight is a
>> success, the status code will still be not found, won't it, if there
>> is no other OPTIONS handler for the resource?
>> Am I misinterpreting?
> There is no status code.
> http://dvcs.w3.org/hg/cors/raw-file/tip/Overview.html#cross-origin-request-status
> is set to "network error" which is on the granularity of failed to connect,
> unknown domain, etc.

That's on the client side, isn't it?. I'm worried about the resource
side. On the resource side, what HTTP status code should be coming
back from server to client for a preflight when the server has no
other OPTIONS to return. 200? or 40x?

> --
> Anne van Kesteren
> http://annevankesteren.nl/
Received on Monday, 5 December 2011 15:57:54 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:37 UTC