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.

Not sure what IE behavior here is.


Reply via email to