You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User context lookup now tags the hash lookup response. The logout listener can now invalidate that tag instead of doing a BAN request. The previous varnish BAN request has been incorrect and banned all cache entries on Varnish.
The logout handler is now also activated by default for the Symfony HttpCache in addition to Varnish and Noop.
Fixed
Cache Tagging: It is now possible to use cache tagging without installing the SensioFrameworkExtraBundle. There is a new configuration option tags.annotations.enabled that can be set to false.
Cache Tagging: Clear the SymfonyResponseTagger after we tagged a response.
Usually PHP uses a new instance for every request. But for example the hash
lookup when using Symfony HttpCache does two requests in the same PHP
process.
Regression in the configuration when you explicitly specified the default
proxy client. This started to be reported as error in 2.3.0 and now works
again.
[Symfony HttpCache] You can now configure the Symfony proxy client to
directly call the HttpCache for invalidation requests instead of executing
real web requests.
Use the new configuration option proxy_client.symfony.use_kernel_dispatcher
and follow the instructions in FOSHttpCache to adjust your kernel and
bootstrap things accordingly.