1.3.13

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

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