- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Wed, 03 Feb 2021 10:18:48 +0000
- To: Julian Reschke <julian.reschke@gmx.de>
- cc: ietf-http-wg@w3.org
-------- Julian Reschke writes: > Am 03.02.2021 um 10:59 schrieb Poul-Henning Kamp: > > -------- > > Julian Reschke writes: > >> Am 03.02.2021 um 10:48 schrieb Poul-Henning Kamp: > >>> -------- > >>> Julian Reschke writes: > >>> > >>>> 1xx messages can not have a message body. > >>> > >>> The message body does not belong to the 142, it belongs to the trailer= > . > >> > >> Trailers in HTTP/1.1 require chunked encoding, thus a message body. You > >> can't send a message body absent a final status code message. > > > > This is not "Trailers in HTTP/1.1", so that is not relevant. > > > > This is a new HTTP extension which makes it possible to transmit a respo= > nse with body and header parts swapped. > > I still don't get how you deploy it in HTTP/1.1. *Only* if a requestor lights whatever "bat-signal" we choose, can the responder send a 142, the chunked body and the headers, in that order. The "bat-signal" should be designed to not pass through intermediaries which do not understand its significance. (ie: hop-by-hop header, mentioned in Connection:) -- 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, 3 February 2021 10:19:03 UTC