Update dependency friendsofsymfony/http-cache-bundle to v2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
friendsofsymfony/http-cache-bundle	require	major	^1.3 -> 2.10.2

---

Release Notes

FriendsOfSymfony/FOSHttpCacheBundle

v2.10.2

Compare Source

Fixed

• The fix about overwriting flash messages on multiple redirects introduced in
  version 2.9.1 created the risk of losing flash messages when redirecting to a
  path that is outside the firewall or destroys the session.
  This version hopefully fixes both cases. Existing flash messages in a request
  cookie are merged with new flash messages from the session.

v2.10.1

Compare Source

Fixed

• Fix typehint in PHP 8 attributes handling to use ControllerResolverInterface

v2.10.0

Compare Source

Changed

• Adjusted to work with PHP 8
• Dropped support for PHP 7.2
• Added support for PHP 8 Attributes

v2.9.2

Compare Source

Fixed

• The fix about overwriting flash messages on multiple redirects introduced in
  version 2.9.1 created the risk of losing flash messages when redirecting to a
  path that is outside the firewall or destroys the session.
  This version hopefully fixes both cases. Existing flash messages in a request
  cookie are merged with new flash messages from the session.

v2.9.1

Compare Source

Fixed

• Flash messages won't be lost even when redirecting multiple times.

v2.9.0

Compare Source

Added

• New Feature: Command fos:httpcache:clear to clear the whole http cache.

v2.8.0

Compare Source

Fixed

• Adjusted to work with Twig 3
• Adjusted to work with Symfony 5
• Allow Httplug 2

v2.7.2

Compare Source

Fixed

• Avoid deprecation warning about ContainerAwareCommand.

v2.7.1

Compare Source

Fixed

• Avoid deprecation warning about TokenInterface::getRoles.
• Improve exception message if a tag capable client is not found.

v2.7.0

Compare Source

Changed

• Allow to use environment variables to configure the caching proxy.

Fixed

• Invalidate the user context cache also when impersonating a user and when stopping to impersonate.

v2.6.1

Compare Source

Fixed

• Do not leak the Symfony-Session-NoAutoCacheControl header when the Symfony session system is not enabled.

v2.6.0

Compare Source

Changed

• 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.

v2.5.1

Compare Source

Fixed

• 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.

v2.5.0

Compare Source

Added

• New Feature: Support for the max_header_value_length option to split huge tag lists into multiple headers. #​483

Fixed

• Cache control on Symfony 4.1 now also works when the Vary header for user_context_hash is already present on the response. #​485

v2.4.1

Compare Source

• Adjust session_listener to work with Symfony 3.4.12 (symfony/symfony#​27467).

v2.4.0

Compare Source

Added

• Support for the Varnish xkey vmod for more efficient cache tagging.

• Autoconfigure support for custom context providers.

• Autowiring support for the services in this bundle:

  • fos_http_cache.cache_manager => FOS\HttpCacheBundle\CacheManager
  • fos_http_cache.http.symfony_response_tagger => FOS\HttpCacheBundle\Http\SymfonyResponseTagger
  • fos_http_cache.event_listener.cache_control => FOS\HttpCacheBundle\EventListener\CacheControlListener
  • fos_http_cache.proxy_client.default => FOS\HttpCache\ProxyClient\ProxyClient

  The old service names are still available, but using them directly is deprecated.

v2.3.1

Compare Source

Fixed

• 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.

v2.3.0

Compare Source

Added

• [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.

v2.2.2

Compare Source

Fixed

• Fix session_listener decoration when session is not enabled.

v2.2.1

Compare Source

Fixed

• Adjust user context listener to handle Symfony 4.1 breaking behaviour change.

v2.2.0

Compare Source

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 the proxy_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 option match.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.
  Value true 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.

v2.1.2

Compare Source

• fixed nginx configuration bug

v2.1.1

Compare Source

• configuring cache tagging is now allowed when the default client is the noop client

v2.1.0

Compare Source

Added

• Individual rules in the cache_control can now again have a match_response
  or additional_response_status configuration to limit the rule to certain
  responses.

  For this, the signature of CacheControlListener::addRule had to be changed.
  It now expects a RuleMatcherInterface instead of the
  ResponseMatcherInterface. If you extended the listener or change the service
  configuration, this could be a BC BREAK for your application.

Fixed

• If no response matching is configured on cache_control, the global
  cacheable configuration is now respected to decide whether cache headers
  should be set. By default, this follows RFC 7234, only responses with status
  200, 203, 204, 206, 300, 301, 404, 405, 410, 414 or 501 get cache headers.

  We decided to consider this a bugfix, but if your relied on this behaviour it
  will be a BC BREAK for your application.

v2.0.0

Compare Source

General

• Updated the version of FOSHttpCache to 2.0.0. See the FOSHttpCache changelog
  for more information. Most importantly, we removed the hard coupling on the
  Guzzle HTTP client (using HTTPlug). Your composer.json now needs to
  specify which HTTP client to install; see the installation instructions
• Deprecated methods have been removed.

Proxy client

• The configuration for the proxy client has been adjusted. Proxy servers are
  now configured under http and servers must be a list - a comma separated
  string of server IPs is no longer supported.

Event listeners

• BC break: the UserContextListener constructor signature was changed to
  take an array of options.
• BC break: renamed the event listener classes to XyzListener.

Rule matcher

• BC break: The match_response and additional_cacheable_status
  configuration parameters were removed for individual match rules.
  Note that match_response and additional_response_status have been re-added for
  cache_control in 2.0.1.

• BC break: The second argument of the RuleMatcher constructor was changed
  to take a ResponseMatcherInterface.

• Cacheable status codes are now configured globally
  (cacheable.response.additional_status or cacheable.response.expression).

Tags

• BC break: The TagHandler has been split. Invalidating tags happens through
  CacheManager::invalidateTags (if you use annotations for tag invalidation, you
  don't need to change anything). Recording tags and writing them into the
  responses is now done through the SymfonyResponseTagger.
  The service fos_http_cache.handler.tag_handler no longer exists. For
  tagging responses, use fos_http_cache.http.symfony_response_tagger instead,
  and to invalidate tags use the service fos_http_cache.cache_manager.
• BC break: The configuration tags.header has been removed. Configuring
  the header for tagging responses is now done at tags.response_header.
  Configuring the header for tag invalidation requests is now done at
  proxy_client.varnish.tags_header.

Tests

• BC break: Dropped the proxy client services as they where not used anywhere. The
  services fos_http_cache.test.client.varnish and
  fos_http_cache.test.client.nginx no longer exist.

User context

• Added an option always_vary_on_context_hash to make it possible to disable
  automatically setting the vary headers for the user hash.

v1.3.16

Compare Source

• Adjust session_listener to work with Symfony 3.4.12 (symfony/symfony#​27467).

v1.3.15

Compare Source

• Fix session_listener decoration when session is not enabled.

v1.3.14

Compare Source

• User context compatibility which was broken due to Symfony making responses
  private if the session is started as of Symfony 3.4+.

v1.3.13

Compare Source

• Symfony HttpCache User Context: Move the AnonymousRequestMatcher to FOSHttpCache.

  The recommended way to ignore cookie based sessions is to set session_name_prefix to
  false rather than omit the Cookie header from user_identifier_headers.

v1.3.12

Compare Source

• Prevent potential accidental caching on user context hash mismatch (particularly with symfony HttpCache).

v1.3.11

Compare Source

• #​395 : Compatibility with SensioFrameworkExtraBundle 4.

v1.3.10

Compare Source

• Avoid calling deprecated method in Symfony 3.2.

v1.3.9

Compare Source

• Fix configuration handling when only custom proxy client is configured.

v1.3.8

Compare Source

• Do not sanity check hash on anonymous requests.

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.