W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2020

Re: Structured Fields: whitespace in binary content

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Wed, 28 Oct 2020 08:37:33 +0000
To: Mark Nottingham <mnot@mnot.net>
cc: HTTP Working Group <ietf-http-wg@w3.org>, Poul-Henning Kamp <phk@varnish-cache.org>
Message-ID: <63185.1603874253@critter.freebsd.dk>
Mark Nottingham writes:

> So, the obvious fix is to allow whitespace inside binary content. 
> Delimitation won't be lost, because it's ":" on both ends. The base64 
> parsers I checked already swallow whitespace in input (not surprising 
> since the motivating use case for base64 was line-wrapped MIME).

I dont see any obvious harm, and being able to "lint" IDs and RFCs
seems a worthwhile argument.

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 Wednesday, 28 October 2020 08:37:52 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 28 October 2020 08:37:53 UTC