Re: 103 Early Hints and Caching Intermediaries


On Tue, Aug 01, 2017 at 10:15:50PM +0200, Felix Hassert wrote:
> To avoid "guessing" in intermediaries, we could define a special Cache Control
> header field accompanying the 103 status, such as "Early-Hint-Control". An
> origin could then define a 103 to be cacheable in a proxy server or cache. For
> subsequent requests the stored 103 could be sent downstream regardless of
> whether the final response is public or private.
> The header field could follow the Cache-Control semantics. The "public" and
> "max-age=N" directives seem appropriate. A proxy server would have to store the
> Early Hint information apart from regular responses (e.g. 200) to not confuse it
> with a final response. When the field "Early-Hint-Control: public" is not
> present, the 103 response should not be stored.

Why not simply use cache-control and define its validity with 103 ? I think
that your use case makes a lot of sense, though in terms of cache, it's
very special in that this cache would probably aggregate all Link header
fields retrieved over possibly multiple 103 responses, never any payload,
and would return them upon further requests.


Received on Tuesday, 1 August 2017 21:04:42 UTC