Skip to content

Releases: FriendsOfSymfony/FOSHttpCacheBundle

1.3.14

14 Apr 09:30
@dbu dbu
1.3.14
Compare
Choose a tag to compare
  • Backported fix for user context caching. The feature has been broken with Symfony 3.4 due to Symfony making responses private if the session is started as of Symfony 3.4+.

2.2.0

23 Mar 15:55
@dbu dbu
2.2.0
Compare
Choose a tag to compare

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.

1.3.13

23 Mar 15:05
@dbu dbu
1.3.13
e8a825b
Compare
Choose a tag to compare
  • 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

12 Jan 17:03
@dbu dbu
2.1.2
Compare
Choose a tag to compare
  • fixed nginx configuration bug

2.2.0-alpha1

09 Nov 20:07
@dbu dbu
97eaf18
Compare
Choose a tag to compare
2.2.0-alpha1 Pre-release
Pre-release

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

09 Nov 19:22
@dbu dbu
22853b5
Compare
Choose a tag to compare
  • Prevent potential accidental caching on user context hash mismatch (particularly with symfony HttpCache)

1.3.11

06 Nov 09:25
@dbu dbu
bcdecd7
Compare
Choose a tag to compare

#395 : Compatibility with SensioFrameworkExtraBundle 4

2.1.1

17 Jul 12:00
@dbu dbu
Compare
Choose a tag to compare
  • configuring cache tagging is now allowed when the default client is the noop client

2.1.0

23 Jun 13:34
@dbu dbu
Compare
Choose a tag to compare
  • 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

10 Jun 17:23
@dbu dbu
2.0.0
Compare
Choose a tag to compare

See CHANGELOG.md for a full list of changes