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

• From: Poul-Henning Kamp <phk@phk.freebsd.dk>
• Date: Tue, 14 Feb 2017 21:11:55 +0000
• To: Loïc Hoguin <essen@ninenines.eu>
• cc: Adrien de Croy <adrien@qbik.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
• Message-ID: <74700.1487106715@critter.freebsd.dk>

--------
In message <e01c4945-1116-d258-7004-ea917843bf3d@ninenines.eu>, =?UTF-8?Q?Lo=c3=afc_Hoguin?= writes:

>    4.  If a message is received without Transfer-Encoding and with
>        either multiple Content-Length header fields having differing
>        field-values or a single Content-Length header field having an
>        invalid value,

Last year, I think, I have had some dude claim that a "valid value"
was a sequence of digits, but that there is no explicit requirement
that it match the length of the body of that request.

I told him to get stuffed.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

Received on Tuesday, 14 February 2017 21:12:28 UTC