Re: [CORS] Charset in content type

On Thu, 19 Mar 2009 20:37:50 +0100, Giovanni Campagna  
<> 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