- From: Willy Tarreau <w@1wt.eu>
- Date: Tue, 11 Apr 2023 16:34:37 +0200
- To: Mark Nottingham <mnot@mnot.net>
- Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, Bertrand Martin <bertrand@sentrysoftware.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On Wed, Apr 12, 2023 at 12:16:28AM +1000, Mark Nottingham wrote: > > > On 12 Apr 2023, at 12:10 am, Lucas Pardue <lucaspardue.24.7@gmail.com> wrote: > > > > Have you considered how this might work where there is a chain of servers > > involved in handling a request? We might think of CDNs in this light but it > > is also common for servers to sit in front of something like an app server > > or cache server. Therefore it could benefit this proposal to make it a list > > of values that can comprise the entire lifecycle of a request/response > > exchange. > > I had the same thought. It's probably best specified as a List of Decimals; see: > https://httpwg.org/specs/rfc8941.html > > But, I also wonder if the response is the best place to put this information > -- it only makes it available after the fact, and scatters information that > needs to be aggregated for many use cases. More discussion / description of > the use cases would help guide the design. Yeah and whether or not the production of the header itself is included in the calculation :-) Willy
Received on Tuesday, 11 April 2023 14:34:50 UTC