Re: Cache control in trailers?

so any policy based on metadata will have to wait until the end to apply 
it.  This is not very workable in many cases.

plenty of people wish to block content by Content-Type, and plenty of 
streams are too big to buffer, and so proxies pass data through as it 
comes.

I think we need metadata up-front, at least the stuff that is immutable 
in order to implement policy based on it.


------ Original Message ------
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
To: "Julian Reschke" <julian.reschke@gmx.de>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Sent: 3/02/2021 11:44:07 pm
Subject: Re: Cache control in trailers?

>--------
>Julian Reschke writes:
>
>>  Furhermore I really do not get why a change in wire format is *needed*.
>>  As Martin said, we can mint a new final status code that indicates that
>>  more status information will be in trailer fields.
>
>And as is said, if 3xx works, I'm fine with that.  142 was just my first mockup.
>
>The crucial thing is that if there are trailers there will be no (metadata) headers.
>
>--
>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 21:41:25 UTC