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

"Adrien de Croy" <adrien@qbik.com> Tue, 14 February 2017 22:18 UTC

Resent-Date: Tue, 14 Feb 2017 22:15:57 +0000
Resent-Message-Id: <E1cdlO9-0007XZ-Oi@frink.w3.org>
From: Adrien de Croy <adrien@qbik.com>
To: Daniel Stenberg <daniel@haxx.se>, Matthew Kerwin <matthew@kerwin.net.au>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Date: Tue, 14 Feb 2017 22:15:14 +0000
Message-Id: <em6d16712e-b70e-4eaf-a8a0-8363c22f66a4@bodybag>
In-Reply-To: <alpine.DEB.2.20.1702142300180.2478@tvnag.unkk.fr>
References: <emdcb96fc0-0d2f-436c-9f1f-05beffe7593e@bodybag> <CACweHNAmVua1Do+g6HzDM==CB3RMrd6_wH1Dz7RoszrW0rZD8Q@mail.gmail.com> <alpine.DEB.2.20.1702142300180.2478@tvnag.unkk.fr>
Reply-To: Adrien de Croy <adrien@qbik.com>
User-Agent: eM_Client/7.0.27943.0
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=122.56.26.1; envelope-from=adrien@qbik.com; helo=smtp.qbik.com
Subject: Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length?
Archived-At: <http://www.w3.org/mid/em6d16712e-b70e-4eaf-a8a0-8363c22f66a4@bodybag>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

Yes, you can do this in a U-A, but in a proxy we have to be strict :)

I guess those sites don't work behind proxies.

Adrien


------ Original Message ------
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>
Sent: 15/02/2017 11:05:12 AM
Subject: Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length?

>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