On 2/19/13 1:51 PM, Anne van Kesteren wrote:
Does that include cases though where the page did set a Content-Type through setRequestHeader()?
That's a good question. I don't remember anymore; I'd have to go read the relevant bugs.
Because technically what Firefox does violates HTTP semantics as not every MIME type allows for a charset parameter.
Indeed. Not sure how worthwhile it is to restrict this sort of thing to text/plain.
-Boris
