Re: dont-revalidate Cache-Control header

Questions:

1. MUST NOT seems too harsh. It'll put UAs that don't yet understand the
directive as non-compliant. And we can't be sure whether there could be
legitimate reasons for UAs to send conditional GET.

2. If the user views a subresource, e.g. an embedded image, directly as a
top resource, and the user refreshes UA, what should UA do? It's unlikely
that UA will refuse to oblige the refresh request.

3. If UA requests an older version of a resource that the server no longer
keeps, how should the server respond? If the server returns the latest
version, it'll compromise the semantics of the URI. This requires clearer
specification.

Zhong Yu
bayou.io