CORS handling of 401 response to preflight incorrect (sends the actual POST anyway)

• Component: Page Loading
• Status: NEW ---

[Boris Zbarsky]

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

[Alexey Proskuryakov]

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.

[Boris Zbarsky]

> 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...

[Alexey Proskuryakov]

Good to know that it has been discussed. Do you have any pointers to that discussion?

[Boris Zbarsky]

Not offhand; I'd have to search the archives, just like you...

[Rob Buis]

We check that response is 200 in validatePreflightResponse and also pass access-control-preflight-request-invalid-status-400.html and access-control-preflight-request-invalid-status-501.html wpt tests, so I think this can be closed.