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

Re: [CORS] Charset in content type

From: Anne van Kesteren <annevk@opera.com>
Date: Thu, 19 Mar 2009 23:13:22 +0100
To: "Giovanni Campagna" <scampa.giovanni@gmail.com>, "Jonas Sicking" <jonas@sicking.cc>
Cc: public-webapps <public-webapps@w3.org>
Message-ID: <op.uq170kon64w2qv@annevk-t60.oslo.opera.com>
On Thu, 19 Mar 2009 20:37:50 +0100, Giovanni Campagna  
<scampa.giovanni@gmail.com> wrote:
> Actually both of them are invalid per RFC2616 and thus should raise  

I do not want to enforce validity in the XMLHttpRequest API. That seems  
inconsistent with other APIs, e.g. the DOM API. (It also seems complex and  
impossible as not all headers are known.)

> 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)

How is it unclear?

Anne van Kesteren
Received on Thursday, 19 March 2009 22:14:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:12:51 UTC