Bug 92755 - CORS handling of 401 response to preflight incorrect (sends the actual POST anyway)
: CORS handling of 401 response to preflight incorrect (sends the actual POST a...
Status: NEW
: WebKit
Page Loading
: 528+ (Nightly build)
: Unspecified Unspecified
: P2 Normal
Assigned To:
: https://bugzilla.mozilla.org/show_bug...
:
:
:
  Show dependency treegraph
 
Reported: 2012-07-31 07:50 PST by
Modified: 2012-07-31 10:18 PST (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2012-07-31 07:50:07 PST
Apparently if a preflight for an XHR POST returns a 401 (due to the site requiring Authorization headers), WebKit will send the main POST anyway, in violation of the spec.  Per spec, non-200 responses to a preflight mean the whole thing should be canceled.

See original report at http://code.google.com/p/chromium/issues/detail?id=139566 and see discussion in https://bugzilla.mozilla.org/show_bug.cgi?id=778548
------- Comment #1 From 2012-07-31 09:58:50 PST -------
Looking at public-webapps thread on the topic, there is a reason provided why the CORS draft specification should be changed (IIS with "Classic Application Pool" cannot be configured otherwise), but there is no explanation of why the requirement is necessary.

What is the reason for the requirement to reject non-200 responses? Given that the server sends Access-Control-* response header fields, it's not clear to me why it's beneficial.
------- Comment #2 From 2012-07-31 10:03:18 PST -------
> What is the reason for the requirement to reject non-200 responses?

You could consider reading the thread in the mail archives that made the decision to do so...
------- Comment #3 From 2012-07-31 10:08:45 PST -------
Good to know that it has been discussed. Do you have any pointers to that discussion?
------- Comment #4 From 2012-07-31 10:18:29 PST -------
Not offhand; I'd have to search the archives, just like you...