Re: [XHR] Content-Length header for data: URLs from Anne van Kesteren on 2013-09-20 (public-webapps@w3.org from July to September 2013)

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 19 Sep 2013 20:52:03 -0400
To: Hallvord Steen <hsteen@mozilla.com>
Cc: public-webapps <public-webapps@w3.org>
Message-ID: <CADnb78hKX=8gLx8DqfW7pUdgmkgSC9AwBZnKoan+_kN+zgFd3w@mail.gmail.com>

On Thu, Sep 19, 2013 at 4:47 PM, Hallvord Steen <hsteen@mozilla.com> wrote:
> I see Gecko "fakes" a Content-Length header (visible to getAllResponseHeaders()) when you load a data: URL with XHR. This is wrong per the spec (which is explicitly requiring only a single Content-Type response header) but it looks more like a feature than a bug.. Should we spec it?

That would prohibit processing the data URL incrementally. Or at least
require you to know the size of it in advance somehow. It's not
entirely clear to me whether imposing such a constrain is desirable.


-- 
http://annevankesteren.nl/

Received on Friday, 20 September 2013 00:52:32 UTC