Releases: FriendsOfSymfony/FOSHttpCacheBundle
2.4.1
- Adjust session_listener to work with Symfony 3.4.12 (symfony/symfony#27467).
- Adjust to configuration builder deprecation from Symfony 4.2
1.3.16
- Adjust session_listener to work with Symfony 3.4.12 (symfony/symfony#27467).
2.4.0
2.3.1
2.3.0
- [Symfony HttpCache] You can now configure the Symfony proxy client to
directly call theHttpCache
for invalidation requests instead of executing
real web requests.
Use the new configuration optionproxy_client.symfony.use_kernel_dispatcher
and follow the instructions in FOSHttpCache to adjust your kernel and
bootstrap things accordingly.
1.3.15
2.2.2
2.2.1
1.3.14
2.2.0
Support for Symfony 4. (Note that only the fos_http_cache.cache_manager
service is public in Symfony 4. Use dependency injection if you need direct
access to other services.)
Added
-
You can now use cache tags and invalidate them with the Symfony
HttpCache
reverse proxy. You can tweak configuration in theproxy_client.symfony
section of the configuration. See the FOSHttpCache documentation for
instructions on how to set up the cache. -
Allow to configure the purge method for the Symfony proxy client.
-
You can now also match requests with regular expressions on the query string.
The new optionmatch.query_string
is available for cache control rules, tags
and invalidation. -
ETags can now be false, strong or weak by setting
headers.etag
option to
"strong"
or"weak"
respectively.
Valuetrue
due to backward compatibility will be resolved as"strong"
.
Fixed
-
The FlashMessageListener has been broken during refactoring for 2.0 and now
works again. Constructor uses an options array. -
Tag annotations now work with SensioFrameworkExtraBundle 4. An accidental
exception prevents using them with FOSHttpCacheBundle 2.0 and 2.1. -
User context is more reliable not cache when the hash mismatches. (E.g. after
login/logout.) -
The
ContextInvalidationLogoutHandler
has been deprecated in favor of the
ContextInvalidationSessionLogoutHandler
. The original handler was called
after the invalidation of the session, and thus did not invalidate the session
it should have but a newly created one. You should remove the deprecated service
fos_http_cache.user_context.logout_handler
from the logout.handlers section
of your firewall configuration. -
User context compatibility which was broken due to Symfony making responses
private if the session is started as of Symfony 3.4+.
Deprecated
- Setting up custom services with the commands provided in this bundle has been
deprecated. The$commandName
constructor argument will be removed in 3.0.