# Client Cache Control Directives

The following table lists the cache control directives supported by an HTTP client.

| Directive | Behavior |
| --- | --- |
| no-cache | Caches cannot use a particular response to satisfy subsequent requests<br>without first revalidating that response with the server. If specific response<br>header fields are specified with this value, the restriction applies only to<br>those header fields within the response. If no response header fields are<br>specified, the restriction applies to the entire response. |
| no-store | Caches must not store any part of a response or any part of the request<br>that invoked it. |
| max-age | The consumer can accept a response whose age is no greater than the<br>specified time in seconds. |
| max-stale | The consumer can accept a response that has exceeded its expiration time.<br>If a value is assigned to max-stale, it represents the number of seconds<br>beyond the expiration time of a response up to which the consumer can still<br>accept that response. If no value is assigned, it means the consumer can<br>accept a stale response of any age. |
| min-fresh | The consumer wants a response that will be still be fresh for at least the<br>specified number of seconds indicated. |
| no-transform | Caches must not modify media type or location of the content in a response<br>between a provider and a consumer. |
| only-if-cached | Caches should return only responses that are currently stored in the<br>cache, and not responses that need to be reloaded or revalidated. |
| cache-extension | Specifies additional extensions to the other cache directives. Extensions<br>might be informational or behavioral. An extended directive is specified in<br>the context of a standard directive, so that applications not understanding<br>the extended directive can at least adhere to the behavior mandated by the<br>standard directive. |