Hi,
Nicolas Chambrier (he's not registered to the list, please keep him in
the CC in your replies) and I came across that case recently:
1) create an XHR object (POST in case it matters)
2) set the Content-Type header explicitly (it changes, but we noticed
it with something like
On Tue, Feb 19, 2013 at 5:51 PM, David Bruant bruan...@gmail.com wrote:
My understanding of the spec is that the charset shouldn't be added,
because:
1) the Content-Type header is in author request header
2) the value is a valid MIME-type (tell me if I'm wrong on this)
3) it does not have a
On 2/19/13 1:40 PM, Anne van Kesteren wrote:
On Tue, Feb 19, 2013 at 5:51 PM, David Bruant bruan...@gmail.com wrote:
My understanding of the spec is that the charset shouldn't be added,
because:
1) the Content-Type header is in author request header
2) the value is a valid MIME-type (tell me if
On Tue, Feb 19, 2013 at 6:44 PM, Boris Zbarsky bzbar...@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. :(
On 2013-02-19 19:51, Anne van Kesteren wrote:
On Tue, Feb 19, 2013 at 6:44 PM, Boris Zbarsky bzbar...@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
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
