On Tue, Feb 19, 2013 at 6:44 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > Note that Firefox adds the charset even if it wasn't set by the page because > web developers were asking for it to aid server-side processing... The > alternative is that the server has no idea what to do with the data. :( Does that include cases though where the page did set a Content-Type through setRequestHeader()? Because technically what Firefox does violates HTTP semantics as not every MIME type allows for a charset parameter. -- http://annevankesteren.nl/Received on Tuesday, 19 February 2013 18:51:50 GMT
This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:57 GMT