Boris Zbarsky wrote:
Julian Reschke wrote:
When setting Content-Type twice, IE7 behaves as specified (sending a
*broken* Content-Type header), while Firefox3 simply sends the second
value that was set.
I should further note that Firefox3 will not send exactly the value that
was set; it will often change the charset param to match the encoding it
actually used for the data.
...
Yes, I noticed that. For instance, it happens for application/..+xml,
where it's really useless. Shouldn't this be restricted to text/*?
BR, Julian
