Sections 3.3.2 and 3.3.3 allow bogus Content-Length?

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

Resent-Date: Tue, 14 Feb 2017 20:50:20 +0000
Resent-Message-Id: <E1cdk3I-00053O-96@frink.w3.org>
From: Adrien de Croy <adrien@qbik.com>
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Date: Tue, 14 Feb 2017 20:49:37 +0000
Message-Id: <emdcb96fc0-0d2f-436c-9f1f-05beffe7593e@bodybag>
Reply-To: Adrien de Croy <adrien@qbik.com>
User-Agent: eM_Client/7.0.27943.0
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="------=_MB368674B7-3DCD-4831-A4D3-232958A328D0"
Received-SPF: pass client-ip=122.56.26.1; envelope-from=adrien@qbik.com; helo=smtp.qbik.com
Subject: Sections 3.3.2 and 3.3.3 allow bogus Content-Length?
Archived-At: <http://www.w3.org/mid/emdcb96fc0-0d2f-436c-9f1f-05beffe7593e@bodybag>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

The language in RFC 7230 section 3.3.2 is extremely non-commital about 
whether Content-Length needs to be correct or not.

I'm currently having a dispute about this with someone who quoted these 
sections at me as being proof that you can use any value for C-L 
regardless of the body length.

I think it could be a lot more forcefully written

Or is the person correct and we don't need to have C-L match the body 
length?

In this particular case the discussion is around request messages.

Adrien

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