W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2009

Re: [CORS] Charset in content type

From: Giovanni Campagna <scampa.giovanni@gmail.com>
Date: Thu, 19 Mar 2009 20:37:50 +0100
Message-ID: <65307430903191237s5704cc60x678c2a602c816419@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: Anne van Kesteren <annevk@opera.com>, public-webapps <public-webapps@w3.org>
2009/3/19 Jonas Sicking <jonas@sicking.cc>:
> [...]
>
> Two things that I think we need to watch out for:
>
> 1. Someone doing
>    xhr.setRequestHeader("Content-Type", "text/plain; application/xml");
>
> 2. Someone doing
>    xhr.setRequestHeader("Content-Type", "text/plain;
> somewierdthing=application/xml");
>
> Especially the first might be tricky since we don't know which
> mimetype the server will use. I was going to make our implementation
> require that there is only one "empty" parameter, and optionally a
> charset.

Actually both of them are invalid per RFC2616 and thus should raise SYNTAX_ERR.
Or actually, they don't per current spec, but I think they should.
(and anyway RFC2616 is not very clear about the field-value production)

> [...]
>
> / Jonas
>
>

Giovanni
Received on Thursday, 19 March 2009 19:38:25 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:30 GMT