The Expires header contains the date/time after which the response is considered stale.
Invalid dates, like the value 0, represent a date in the past and mean that the resource is already expired.
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 |
Expires: <http-date>
An HTTP-date timestamp.
Expires: Wed, 21 Oct 2015 07:28:00 GMT
| Specification | Title |
|---|---|
| RFC 7234, section 5.3: Expires | Hypertext Transfer Protocol (HTTP/1.1): Caching |
| Desktop | ||||||
|---|---|---|---|---|---|---|
| Chrome | Edge | Firefox | Internet Explorer | Opera | Safari | |
| Basic support | Yes | Yes | Yes | Yes | Yes | Yes |
| Mobile | |||||||
|---|---|---|---|---|---|---|---|
| Android webview | Chrome for Android | Edge Mobile | Firefox for Android | Opera for Android | iOS Safari | Samsung Internet | |
| Basic support | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
© 2005–2018 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Expires