2.16.2

Fixed

• The new EventDispatchingHttpCache::forward method added in 2.16.0 was not
  compatible with Symfony 4.4. Adjusted the signature to make it compatible.

2.16.1

(Mistake, same as 2.16.0)

3.1.0

Symfony HttpCache

• Add events PRE_FORWARD and POST_FORWARD to allow event listeners to alter
  the request before and after it is sent to the backend.
• Changed CustomTtlListener to use the POST_FORWARD event instead of
  PRE_STORE. Using PRE_STORE, requests that are not considered cacheable by
  Symfony were never cached, even when they had a custom TTL header.
• Add flag fallbackToSmaxage to CustomTtlListener to allow controlling
  fallback to s-maxage if custom TTL header is not defined on the response.
• Fix: Do not call store if Response object is not longer cacheable after event
  listeners. If you use the custom TTL system, this is only a performance
  improvement, because the TTL of the response would still be 0. With a custom
  listener that changes the response explicitly to not be cached but does not
  change s-maxage, this bug might have led to caching responses that should not
  have been cached.

2.16.0

Symfony HttpCache

• Add events PRE_FORWARD and POST_FORWARD to allow event listeners to alter
  the request before and after it is sent to the backend.
• Changed CustomTtlListener to use the POST_FORWARD event instead of
  PRE_STORE. Using PRE_STORE, requests that are not considered cacheable by
  Symfony were never cached, even when they had a custom TTL header.
• Add flag fallbackToSmaxage to CustomTtlListener to allow controlling
  fallback to s-maxage if custom TTL header is not defined on the response.
• Fix: Do not call store if Response object is not longer cacheable after event
  listeners. If you use the custom TTL system, this is only a performance
  improvement, because the TTL of the response would still be 0. With a custom
  listener that changes the response explicitly to not be cached but does not
  change s-maxage, this bug might have led to caching responses that should not
  have been cached.

3.0.0

• Support Symfony 7
• Drop support for Symfony < 6.4
• Test with PHP 8.2 and 8.3
• Drop support for PHP < 8.1
• Switched to PSR-17 message factories
• Switched some places to PSR-18 HTTP client. The main functionality needs the Httplug Async Client specification. There is no PSR for asynchronous clients.
• Parameter and return type declarations where possible.
• Ignore empty tag lists passed to TagCapable::invalidateTags so you don't need to check if there are tags or not.

2.15.3

• Avoid deprecated RequestMatcher in favor of IpsRequestMatcher.

2.15.2

• Declare incompatibility with Symfony 7 because it removes RequestMatcher.

2.15.1

• Directly require php-http/message-factory to keep working with the legacy factories.

2.15.0

• Provide a TagHeaderParser that can split up a tag header into the list of tags.
  This allows to correctly handle non-default tag separators in all places.

2.14.2

• Fixed varnish configuration examples to say Authorization and not Autorization.