| Summary: | XMLHttpRequest shouldn't honor a charset specified via setRequestHeader | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> | ||||
| Component: | XML | Assignee: | Alexey Proskuryakov <ap> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | ||||||
| Priority: | P2 | ||||||
| Version: | 420+ | ||||||
| Hardware: | Mac | ||||||
| OS: | OS X 10.4 | ||||||
| Attachments: |
|
||||||
Created attachment 12298 [details]
proposed patch
Comment on attachment 12298 [details]
proposed patch
r=me
Committed revision 18675. |
Overriding Content-Type as req.setRequestHeader("Content-Type", "text/plain; charset='some-encoding'"); req.send(aString); makes the sent string be encoded as "some-encoding" in WebKit, but not in MSIE or Firefox, where it's always sent as UTF-8. The XMLHttpRequest spec draft mandates IE/Firefox behavior, of course. Additionally, looking at Content-Type further complicates the choice of encoding for documents, see bug 11695.