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 I'm wrong on this)
3) it does not have a charset parameter (so, the condition of step 4 doesn't
apply in my opinion).
Who should I file a bug against?
Firefox.
http://xhr.spec.whatwg.org/#the-send%28%29-method is pretty clear that
we only correct charset parameters. Even if
application/vnd.ooz.user.v1+json was invalid we still should not
muddle with it.
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. :(
-Boris
