[Webkit-unassigned] [Bug 92755] CORS handling of 401 response to preflight incorrect (sends the actual POST anyway)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=92755


Alexey Proskuryakov <ap at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|New Bugs                    |Page Loading
                 CC|                            |abarth at webkit.org,
                   |                            |ap at webkit.org




--- Comment #1 from Alexey Proskuryakov <ap at webkit.org>  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.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.