> I don't think so. IINM, HTTP caching only comes into play when a client
sends a subsequent HTTP request message that may (or may not) be
satisfied by a cached HTTP response message.
A client that follows caching shouldn't send a new request if the cache-control
headers on the first response direct it not to, right?
> Clients could also use If-Modified-Since, right?
Good point.
Then maybe the errata could just be
Clients SHOULD use an If-Modified-Since header to get more effective
caching.
_______________________________________________
Acme mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/acme