Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitf64f6f0

Browse files
committed
minor#7601 Improve specification explanation (matthieu88160, javiereguiluz)
This PR was submitted for the 3.2 branch but it was merged into the 2.7 branch instead (closes#7601).Discussion----------Improve specification explanationRFC 2616 and RFC 7234 define that a recipient MUST ignore Expires header if one of `s-max-age` or `max-age` header is defined.Commits-------ce64af5 Update expiration.rst46e6408 Update expiration.rstb66e4d7 Update expiration.rst13102da Update expiration.rst8666bed Minor reword and fixed the line length232c029 Improve specification explanation
2 parents4de8599 +ce64af5 commitf64f6f0

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

‎http_cache/expiration.rst‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -85,5 +85,12 @@ 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 is
91+
ignored when ``s-maxage`` or ``max-age`` directives are defined.
92+
93+
8894
.. _`expiration model`:http://tools.ietf.org/html/rfc2616#section-13.2
8995
.. _`FrameworkExtraBundle documentation`:https://symfony.com/doc/current/bundles/SensioFrameworkExtraBundle/annotations/cache.html
96+
.. _`RFC 7234 - Caching`:https://tools.ietf.org/html/rfc7234#section-4.2.1

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp