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

[bugzilla-daemon at webkit.org]

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





--- Comment #5 from Sky Sanders <sky.sanders at gmail.com>  2010-12-13 15:00:06 PST ---
OOPS - Sorry, it is when GET content-type is set to application/json that the CORS GET fails.

Setting content-type to text/plain produces a successful CORS GET.

The problem with this, aside from the fact that the spec allows for content-type on a GET, is that the request content type is relevant to many json service implementations and omitting it requires, in most cases, modification to javascript frameworks and server side code, both of which I have had to implement to work around this issue.

please correct me if I have erred in my observations/conclusions.

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