Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length?

Daniel Stenberg <daniel@haxx.se> Tue, 14 February 2017 22:08 UTC

Resent-Date: Tue, 14 Feb 2017 22:06:40 +0000
Resent-Message-Id: <E1cdlFA-0008Sb-UB@frink.w3.org>
Date: Tue, 14 Feb 2017 23:05:12 +0100
From: Daniel Stenberg <daniel@haxx.se>
To: Matthew Kerwin <matthew@kerwin.net.au>
cc: Adrien de Croy <adrien@qbik.com>, HTTP Working Group <ietf-http-wg@w3.org>
In-Reply-To: <CACweHNAmVua1Do+g6HzDM==CB3RMrd6_wH1Dz7RoszrW0rZD8Q@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1702142300180.2478@tvnag.unkk.fr>
References: <emdcb96fc0-0d2f-436c-9f1f-05beffe7593e@bodybag> <CACweHNAmVua1Do+g6HzDM==CB3RMrd6_wH1Dz7RoszrW0rZD8Q@mail.gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Received-SPF: pass client-ip=80.67.6.50; envelope-from=daniel@haxx.se; helo=giant.haxx.se
Subject: Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length?
Archived-At: <http://www.w3.org/mid/alpine.DEB.2.20.1702142300180.2478@tvnag.unkk.fr>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

On Wed, 15 Feb 2017, Matthew Kerwin wrote:

> That, along with everything else in 3.3.2 & 3.3.3, and 3.4 makes me wonder 
> how anyone could find ambiguity there. If C-L is present, it has to be 
> correct.

... but we still see a significant amount of content on the web today that 
serve bodies with sizes that aren't matching the C-L value.

I went several rounds against that, trying to make Firefox's C-L checks 
stricter, but finally lost in the end and had to resort to keeping funky 
heuristics and guessworks.

The web is a harsh place! =)

-- 

  / daniel.haxx.se

Sections 3.3.2 and 3.3.3 allow bogus Content-Leng… Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Loïc Hoguin
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Poul-Henning Kamp
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
RE: Sections 3.3.2 and 3.3.3 allow bogus Content-… Mike Bishop
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Matthew Kerwin
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Jason T. Greene
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Jacob Champion
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Poul-Henning Kamp
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Daniel Stenberg
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Willy Tarreau
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Alex Rousskov
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Jacob Champion
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Alex Rousskov
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Jacob Champion
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Alex Rousskov
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Alex Rousskov
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Matthew Kerwin
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Adrien de Croy
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Alex Rousskov
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Mark Nottingham
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Willy Tarreau
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Poul-Henning Kamp
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Cory Benfield
Re: Sections 3.3.2 and 3.3.3 allow bogus Content-… Patrick McManus