2.1.2

• fixed nginx configuration bug

2.2.0-alpha1

First pre-release of 2.2

Changelog

Added

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

Todo

• Pending a cleanup of the context invalidation during logout (#394)
• Stable version will wait for PHP 7.2 stable and Symfony 3.4/4.0 to be sure we can support those properly in the 2.2 version
• Adjustments to new FOSHttpCache library features

1.3.12

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

1.3.11

#395 : Compatibility with SensioFrameworkExtraBundle 4

2.1.1

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

2.1.0

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

• If no response matching is configured on cache_control, the global
  cacheable configuration is now respected to decide whether cache headers
  should be set.

2.0.0

See CHANGELOG.md for a full list of changes

2.0.0-beta2

adjust dependency on http-cache library

2.0.0-beta1

No functional changes since 2.0.0-alpha1

2.0.0-alpha1

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.

• 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 the
  CacheManager (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.

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.