Connected: An Internet Encyclopedia
13.1.3 Cache-control Mechanisms

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 2068
Up: 13 Caching in HTTP
Up: 13.1 Client Interaction
Prev: 13.1.2 Warnings
Next: 13.1.4 Explicit User Agent Warnings

13.1.3 Cache-control Mechanisms

13.1.3 Cache-control Mechanisms

The basic cache mechanisms in HTTP/1.1 (server-specified expiration times and validators) are implicit directives to caches. In some cases, a server or client may need to provide explicit directives to the HTTP caches. We use the Cache-Control header for this purpose.

The Cache-Control header allows a client or server to transmit a variety of directives in either requests or responses. These directives typically override the default caching algorithms. As a general rule, if there is any apparent conflict between header values, the most restrictive interpretation should be applied (that is, the one that is most likely to preserve semantic transparency). However, in some cases, Cache-Control directives are explicitly specified as weakening the approximation of semantic transparency (for example, "max-stale" or "public").

The Cache-Control directives are described in detail in section 14.9.


Next: 13.1.4 Explicit User Agent Warnings

Connected: An Internet Encyclopedia
13.1.3 Cache-control Mechanisms