Expires
Baseline Widely available
This feature is well established and works across many devices and browser versions. It’s been available across browsers since July 2015.
The Expires HTTP header contains the date/time after which the
response is considered expired.
Invalid expiration dates with value 0 represent a date in the past and mean that the resource is already expired.
Note: If there is a Cache-Control header
with the max-age or s-maxage directive in the response,
the Expires header is ignored.
| Header type | Response header |
|---|---|
| Forbidden header name | no |
| CORS-safelisted response header | yes |
Syntax
http
Expires: <http-date>
Directives
- <http-date>
-
An HTTP-date timestamp.
Examples
http
Expires: Wed, 21 Oct 2015 07:28:00 GMT
Specifications
| Specification |
|---|
| HTTP Caching # field.expires |
Browser compatibility
BCD tables only load in the browser