New in Symfony 3.2: HttpFoundation improvements
Improved the the response cache headers¶
Previously, if you performed a
301 permanent redirect and didn't set a cache
no-cache header was added by Symfony. In Symfony 3.2 this
behavior has changed and now
301 redirects don't add the
automatically, but they maintain it if you set it explicitly.
Symfony 3.2 also fixes another inconsistency related to cache headers. When the
no-cache header is present, Symfony now also adds the
so the response contains
no-cache, private instead of just
HTTP safe methods are those that just retrieve resources but don't modify,
delete or create them (only
HEAD methods are considered safe).
Request class includes a
isMethodSafe() method to check whether the
given HTTP method is considered safe or not.
HTTP idempotent methods are those that can be used in a sequence of several
requests and get the same result without any other side-effect. For example
PUT is idempotent because after two identical requests the resource has
still the same state (it's always replaced) but
POST is not idempotent
because after two identical requests you will end up with two resources that
have the same content.
In Symfony 3.2 we added a new method called
isMethodIdempotent() to check
whether the given HTTP method is idempotent or not.
New in Symfony 3.2: HttpFoundation improvements symfony.com/blog/new-in-symfony-3-2-httpfoundation-improvementsTweet this
Become a certified developer! Exams are online and available in all countries.Register Now
Comments are closed.
To ensure that comments stay relevant, they are closed for old posts.