[Webkit-unassigned] [Bug 11049] XMLHttpRequest always defaults Content-Type to application/xml, while it should depend on data type

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Nov 6 11:51:00 PST 2009


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





--- Comment #11 from Carol Szabo <carol.szabo at nokia.com>  2009-11-06 11:50:59 PDT ---
(In reply to comment #10)
> (In reply to comment #8)
> > Since the risk of breaking anything through this change is low
> 
> How did you determine that?

Since IE does not send back any Content-Type and most websites work with IE, I
assume that all those websites do not care about the Content-Type, they just
assume the content is formatted as they expect it.
Furthermore, if somebody was careless enough to not set a content type on their
post it sounds improbable to me that they would be careful to check if the
content-arrives with the right type at the other end.
Since cross-site XHR is experimental, I assumed that the same team if not
person designed both the JS sending the XHR and the code receiving it.
Pretty much this is my reasoning and I am aware that it is not bullet proof,
but I weigh heavily conformance to standards, versus maintaining legacy dubious
behavior after the standard is relatively solid.
If both IE and Mozilla had the same behavior, I would have agreed that there is
a de facto standard whose legacy we should be mindful of, but since handling
has not been consistent in the past, and the standard seems to be sensible I
would suggest that we move on and support it.

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



More information about the webkit-unassigned mailing list