Commit232c029

authored and

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 parent4de8599 commit232c029Copy full SHA for 232c029

File tree

-0

lines changed

-0

lines changed

Lines changed: 6 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -85,5 +85,11 @@ the lifetime calculation vulnerable to clock skew. Another limitation`
`85`	`85`	of the ``Expires`` header is that the specification states that "HTTP/1.1
`86`	`86`	servers should not send ``Expires`` dates more than one year in the future."
`87`	`87`
	`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`	`+`
`88`	`93`	.. _`expiration model`:http://tools.ietf.org/html/rfc2616#section-13.2
`89`	`94`	.. _`FrameworkExtraBundle documentation`:https://symfony.com/doc/current/bundles/SensioFrameworkExtraBundle/annotations/cache.html
	`95`	+.. _`RFC 7234 - Caching`:https://tools.ietf.org/html/rfc7234

Comments

(0)