WARNING: You are browsing the documentation for Symfony 4.1 which is not maintained anymore. Consider upgrading your projects to Symfony 4.3.

You are browsing the Symfony 4.1 documentation, which changes significantly from Symfony 3.x. If your app doesn't use Symfony 4.1 yet, browse the Symfony 3.4 documentation.

HTTP Cache Expiration

4.1 version

Maintained

3.4 4.3 current 4.4 5.0 master

Unmaintained

2.7 2.8 3.0 3.1 3.2 3.3 4.0 4.2

HTTP Cache Expiration
- Expiration with the Cache-Control Header
- Expiration with the Expires Header

HTTP Cache Expiration¶

The expiration model is the most efficient and straightforward of the two caching models and should be used whenever possible. When a response is cached with an expiration, the cache returns it directly without hitting the application until the cached response expires.

The expiration model can be accomplished using one of two, nearly identical, HTTP headers: Expires or Cache-Control.

You can use both validation and expiration within the same Response. As expiration wins over validation, you can benefit from the best of both worlds. In other words, by using both expiration and validation, you can instruct the cache to serve the cached content, while checking back at some interval (the expiration) to verify that the content is still valid.

Tip

You can also define HTTP caching headers for expiration and validation by using annotations. See the FrameworkExtraBundle documentation.

Expiration with the `Cache-Control` Header¶

Most of the time, you will use the Cache-Control header. Recall that the Cache-Control header is used to specify many different cache directives:

// sets the number of seconds after which the response
// should no longer be considered fresh by shared caches
$response->setSharedMaxAge(600);

The Cache-Control header would take on the following format (it may have additional directives):

1	Cache-Control: public, s-maxage=600

Expiration with the `Expires` Header¶

An alternative to the Cache-Control header is Expires. There's no advantage or disadvantage to either: they're just different ways to set expiration caching on your response.

According to the HTTP specification, "the Expires header field gives the date/time after which the response is considered stale." The Expires header can be set with the setExpires() Response method. It takes a DateTime instance as an argument:

$date = new DateTime();
$date->modify('+600 seconds');

$response->setExpires($date);

The resulting HTTP header will look like this:

1	Expires: Thu, 01 Mar 2011 16:00:00 GMT

Note

The setExpires() method automatically converts the date to the GMT timezone as required by the specification.

Note that in HTTP versions before 1.1 the origin server wasn't required to send the Date header. Consequently, the cache (e.g. the browser) might need to rely on the local clock to evaluate the Expires header making the lifetime calculation vulnerable to clock skew. Another limitation of the Expires header is that the specification states that "HTTP/1.1 servers should not send Expires dates more than one year in the future."

Note

According to RFC 7234 - Caching, the Expires header value is ignored when the s-maxage or max-age directive of the Cache-Control header is defined.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.

HTTP Cache Expiration

HTTP Cache Expiration¶

Expiration with the Cache-Control Header¶

Expiration with the Expires Header¶

Expiration with the `Cache-Control` Header¶

Expiration with the `Expires` Header¶