Re: Cache control in trailers?

On Fri, Feb 05, 2021 at 09:12:48PM +0000, Adrien de Croy wrote:
> 
> 
> ------ Original Message ------
> From: "Roy T. Fielding" <fielding@gbiv.com>
> 
> > Personally, I think end-status is the easiest and most reusable solution, for
> > any number of features that might need to know if something broke. However,
> > Willy is right that saying must-revalidate up front and then softening that
> > at the end would be the safer choice where completion is more important
> > than default performance. I suggest that choice needs to be resource-specific.
> > 
> > 
> The "Something broke" could also apply to a scanning intermediary.  E.g.
> some message body was found to contain a virus.
> 
> If an intermediary could signal that the final status may be different, and
> rely on clients to obey that, then it could safely stream unscanned data to
> the client, and indicate the result at the end, knowing the client will
> discard the message body.

Or even better, indicate a suspected infection so that the client can
apply extra measures including quarantine, second inspection, ask user
for consent etc, which are not possible today.

This is a very good idea which illustrates very well how passing metadata
after a body can be beneficial.

Willy

Received on Saturday, 6 February 2021 08:09:33 UTC