- From: David Bruant <bruant.d@gmail.com>
- Date: Tue, 19 Feb 2013 18:51:11 +0100
- To: public-webapps@w3.org
- CC: Nicolas Chambrier <naholyr@gmail.com>
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 "application/vnd.ooz.user.v1+json") 3) .send() (what is sent is a JSON valid string) Firefox adds a "; charset=UTF-8" after the manually set content-type value. Chrome does not. I'd like to report a bug, but I'm not sure where I should report it to :-s 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? David
Received on Tuesday, 19 February 2013 17:51:42 UTC