[Webkit-unassigned] [Bug 50773] CORS origin header not set on GET when content type request header is set

Thu Feb 3 03:05:25 PST 2011

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

Martin Galpin <galpin at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |galpin at gmail.com

--- Comment #8 from Martin Galpin <galpin at gmail.com>  2011-02-03 03:05:25 PST ---
I can confirm this is still an issue on WebKit (and Chrome). Let me add some additional comments.

* The issue is not with a specific Content-Type (although it can be triggered by using a content-type not listed in CORS spec. [2.1])

* The problem is that in non-simple GET requests (those that require a preflight OPTIONS request), the Origin header is correctly sent with the OPTIONS but not the subsequent GET. Therefore, a server does not include the Access-Control-Allow-Origin in its response.

This has been previously reported in Chromium, see http://code.google.com/p/chromium/issues/detail?id=57836 and includes a matrix of requests.

What can we do to get this fixed?

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