- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Tue, 11 Apr 2023 14:26:02 +0000
- To: Lucas Pardue <lucaspardue.24.7@gmail.com>
- cc: Bertrand Martin <bertrand@sentrysoftware.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Lucas Pardue writes: > Therefore it could benefit this proposal to make it a list of > values that can comprise the entire lifecycle of a request/response > exchange. Personally I would prefer it just be a single number to prevent finger-printing, information-leakage etc. But speaking of "entire lifecycle": A caching intermediary which do not understand the new header will "charge" the full cost of the backend-procesing to all clients - also the ones which get a cache hit and never activate the backend. If the numbers have to have meaning, the new header MUST be hop-by-hop, so that the client can trust that all layers in the sandwich has performed proper accounting. -- 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 Tuesday, 11 April 2023 14:26:08 UTC