Closed Bug 703548 Opened 13 years ago Closed 2 years ago

ajax request: utf-8 is added despite charset being set

Categories

(Firefox :: General, defect)

8 Branch
x86
macOS
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: werner.punz, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20100101 Firefox/8.0
Build ID: 20111104165243

Steps to reproduce:

I created a page which uses iso-8859-15 as encoding and I am sending an ajax request:
with following content type:  application/x-www-form-...ed; charset:ISO-8859-15



Actual results:


Now the follwing happens upon issuing the request following content type is issued
application/x-www-form-...ed; charset:utf-8; charset:ISO-8859-15

So Firefox appens utf-8 ignoring both the page content type and the content type passed down already, which results in a bogus request and/or wrong encoding.



Expected results:

The content type passed down should look like the initial one, every other browser does not have this issue.
Ok correction, I found a small bug in my code. Now the encoding is passed down properly. And I get another bug:
When I pass down application/x-www-form-...ed; charset=ISO-8859-15
Firebug shows me that UTF-8 is passed down as request header application/x-www-form-...ed; charset=UTF-8

All other browsers correctly pass down the original request header.
Severity: normal → major
Ok I did a server side test. Firefox indeed enforces a content-type of UTF-8 no matter what content type is passed down on the client. The charset passed down by the client simply is ignored. This is indeed a bug.
QA Whiteboard: qa-not-actionable

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: major → --

Unfortunately, this never got progressed, and the reporter is now inactive. Marking as incomplete, if this is still an issue, I'm sure someone would raise it.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.