- From: Greg Wilkins <gregw@webtide.com>
- Date: Fri, 5 Feb 2021 10:00:31 +0100
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Received on Friday, 5 February 2021 09:00:59 UTC
On Fri, 5 Feb 2021 at 09:41, Julian Reschke <julian.reschke@gmx.de> wrote: > > Note: "Etag" is already marked as acceptable in trailers > (<https://github.com/httpwg/http-core/issues/262>). > Sure, but one of the suggestions to come out of this thread is that it might be valuable to put something in the header to say that the final value will be in the trailers. This could be for an individual header (eg Willy suggested Cache-Control: no-cache; trailers) or a more general mechanism like the 3xx proposal. So in the case of Etag, would it be worthwhile for cache implementers to know that the content they are currently receiving will/may have an etag in the trailers? If so, that suggests a more general mechanism for hinting at the contents of the trailers is needed. It is hard to focus on actual solutions whilst the scope of the issue is not resolved. cheers -- Greg Wilkins <gregw@webtide.com> CTO http://webtide.com
Received on Friday, 5 February 2021 09:00:59 UTC