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

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

Resent-Date: Tue, 14 Feb 2017 23:35:10 +0000
Resent-Message-Id: <E1cdmco-0000PJ-7K@frink.w3.org>
From: Adrien de Croy <adrien@qbik.com>
To: Jacob Champion <champion.p@gmail.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Date: Tue, 14 Feb 2017 23:34:30 +0000
Message-Id: <em7388b077-40e2-44f9-8bda-914315cd1442@bodybag>
In-Reply-To: <abf8f814-2eb3-87fa-a692-17e5d05313d7@gmail.com>
References: <emdcb96fc0-0d2f-436c-9f1f-05beffe7593e@bodybag> <e01c4945-1116-d258-7004-ea917843bf3d@ninenines.eu> <ema747b801-6dcc-4b2d-ac95-9a027e10c0b4@bodybag> <7874c62b-c6a0-5d84-8115-20016b45118a@measurement-factory.com> <em541e3407-4e99-468e-a1e7-85a7bf074bdd@bodybag> <874938e6-2153-e02a-ab0e-814f468c58f8@measurement-factory.com> <em95b13204-3a33-4bd5-81d2-791e809b9cd2@bodybag> <abf8f814-2eb3-87fa-a692-17e5d05313d7@gmail.com>
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/em7388b077-40e2-44f9-8bda-914315cd1442@bodybag>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

A receiver cannot.

A sender can however (e.g. get file size, string length whatever).

A receiver therefore depends on the sender sending the correct value.

This is presuming the sender knows the length.  If the sender doesn't 
know the length it should not (MUST) set Content-Length header, but 
instead use chunking.

------ Original Message ------
From: "Jacob Champion" <champion.p@gmail.com>
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Sent: 15/02/2017 12:24:48 PM
Subject: Re: Sections 3.3.2 and 3.3.3 allow bogus Content-Length?

>On 02/14/2017 03:18 PM, Adrien de Croy wrote:
>>The only true size of a body is what you obtain by counting its bytes.
>
>Can you explain how you would count the bytes in a message body if you 
>don't know where that body ends?
>
>--Jacob
>

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