[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
Mon Dec 21 10:17:25 PST 2009


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





--- Comment #18 from Carol Szabo <carol.szabo at nokia.com>  2009-12-21 10:17:24 PST ---
(In reply to comment #17)
> (From update of attachment 45336 [details])
> I'm against changing our behavior to something that matches no other browser.
> We can revisit this once Mozilla takes some action with the bug Anne filed.
> 
> The fact that IE and Firefox behave differently gives some hope for servers not
> depending on either behavior, but it is also quite probable that client-side JS
> has different code paths for different browsers, adjusting Content-Type as
> necessary.

This bug only applies to cases when JS writers do not actually care to set the
content type, hence they do not have different paths for Mozilla and IE in this
regard.
Yes, you are right that probably servers do not care, or otherwise IE or
Mozilla would not work, but wouldn't it be nice for WebKit to set a good
example and be the first to do the reasonable thing.

If somebody in power (i.e. reviewer) is staunchly opposed to doing anything on
this issue, which is indeed of minute importance, maybe it would be productive
to close the bug as won't fix, so that test developers know what to expect, and
others stop wasting time trying to address it, maybe Anne can be convinced to
change the standard by vigurous opposition to actually implementing it, which I
personally would not like, but it seems better than the status quo, where we
have a standard to which the major players do not adhere and there is no
movement toward it either.

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