- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 3 Feb 2021 10:26:48 +0100
- To: ietf-http-wg@w3.org
Am 03.02.2021 um 09:22 schrieb Poul-Henning Kamp: > -------- > Mark Nottingham writes: > >> One of the fundamental limitations of HTTP that people often bump into >> is that the status code and headers precede the body,[1] so if something >> goes wrong while the response is being generated, they can get into >> awkward situations. > > ...and having an ambiguity between headers and trailers will make for even more awkward situations. > > As far as I can tell, allowing trailers to change anything fundamental about the object just shifts the need to buffer the entire object to the next step in the food-chain. > > But that can still be a significant improvement, because production and transmission overlaps. > > If we want enable that, we should move *all* headers and status to the trailer, so that no confusion is possible. > > The way to do that is to define a new 1xx status code, which says the body comes first and should not be touched until trailers tell what it is. > > Since there is no credible use-case where the content-length is already known, for HTTP/1.1 chunked encoding can be implied by the 1xx code. > ... 1xx messages can not have a message body. Best regards, Julian
Received on Wednesday, 3 February 2021 09:27:04 UTC