Releases: FriendsOfSymfony/FOSHttpCache
Releases · FriendsOfSymfony/FOSHttpCache
3.1.1
2.16.2
2.16.1
3.1.0
Symfony HttpCache
- Add events 
PRE_FORWARDandPOST_FORWARDto allow event listeners to alter
the request before and after it is sent to the backend. - Changed CustomTtlListener to use the 
POST_FORWARDevent instead of
PRE_STORE. UsingPRE_STORE, requests that are not considered cacheable by
Symfony were never cached, even when they had a custom TTL header. - Add flag 
fallbackToSmaxagetoCustomTtlListenerto allow controlling
fallback tos-maxageif custom TTL header is not defined on the response. - Fix: Do not call store if Response object is not longer cacheable after event
listeners. If you use the custom TTL system, this is only a performance
improvement, because the TTL of the response would still be 0. With a custom
listener that changes the response explicitly to not be cached but does not
changes-maxage, this bug might have led to caching responses that should not
have been cached. 
2.16.0
Symfony HttpCache
- Add events 
PRE_FORWARDandPOST_FORWARDto allow event listeners to alter
the request before and after it is sent to the backend. - Changed CustomTtlListener to use the 
POST_FORWARDevent instead of
PRE_STORE. UsingPRE_STORE, requests that are not considered cacheable by
Symfony were never cached, even when they had a custom TTL header. - Add flag 
fallbackToSmaxagetoCustomTtlListenerto allow controlling
fallback tos-maxageif custom TTL header is not defined on the response. - Fix: Do not call store if Response object is not longer cacheable after event
listeners. If you use the custom TTL system, this is only a performance
improvement, because the TTL of the response would still be 0. With a custom
listener that changes the response explicitly to not be cached but does not
changes-maxage, this bug might have led to caching responses that should not
have been cached. 
3.0.0
- Support Symfony 7
 - Drop support for Symfony < 6.4
 - Test with PHP 8.2 and 8.3
 - Drop support for PHP < 8.1
 - Switched to PSR-17 message factories
 - Switched some places to PSR-18 HTTP client. The main functionality needs the Httplug Async Client specification. There is no PSR for asynchronous clients.
 - Parameter and return type declarations where possible.
 - Ignore empty tag lists passed to 
TagCapable::invalidateTagsso you don't need to check if there are tags or not.