Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 232c029

Browse files
matthieu88160xabbuh
matthieu88160
authored and
xabbuh
committed
Improve specification explanation
RFC 2616 and RFC 7234 define that a recipient MUST ignore Expires header if one of `s-max-age` or `max-age` header is defined.
1 parent 4de8599 commit 232c029

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

‎http_cache/expiration.rst

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -85,5 +85,11 @@ the lifetime calculation vulnerable to clock skew. Another limitation
8585
of the ``Expires`` header is that the specification states that "HTTP/1.1
8686
servers should not send ``Expires`` dates more than one year in the future."
8787

88+
.. note::
89+
90+
Accordingly with `RFC 7234 - Caching`_, the `Expires` header value will be ignored by any recipient if a `s-max-age` or `max-age` header is defined.
91+
92+
8893
.. _`expiration model`: http://tools.ietf.org/html/rfc2616#section-13.2
8994
.. _`FrameworkExtraBundle documentation`: https://symfony.com/doc/current/bundles/SensioFrameworkExtraBundle/annotations/cache.html
95+
.. _`RFC 7234 - Caching`: https://tools.ietf.org/html/rfc7234

0 commit comments

Comments
 (0)