Update dependency friendsofsymfony/http-cache-bundle to v2 #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.3
->2.10.2
Release Notes
FriendsOfSymfony/FOSHttpCacheBundle
v2.10.2
Compare Source
Fixed
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
v2.10.0
Compare Source
Changed
v2.9.2
Compare Source
Fixed
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
v2.9.0
Compare Source
Added
fos:httpcache:clear
to clear the whole http cache.v2.8.0
Compare Source
Fixed
v2.7.2
Compare Source
Fixed
ContainerAwareCommand
.v2.7.1
Compare Source
Fixed
TokenInterface::getRoles
.v2.7.0
Compare Source
Changed
Fixed
v2.6.1
Compare Source
Fixed
Symfony-Session-NoAutoCacheControl
header when the Symfony session system is not enabled.v2.6.0
Compare Source
Changed
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
SensioFrameworkExtraBundle
. There is a new configuration optiontags.annotations.enabled
that can be set tofalse
.v2.5.1
Compare Source
Fixed
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
Fixed
v2.4.1
Compare Source
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:
The old service names are still available, but using them directly is deprecated.
v2.3.1
Compare Source
Fixed
default
proxy client. This started to be reported as error in 2.3.0 and now works
again.
v2.3.0
Compare Source
Added
directly call the
HttpCache
for invalidation requests instead of executingreal 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
session_listener
decoration when session is not enabled.v2.2.1
Compare Source
Fixed
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, tagsand 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 theContextInvalidationSessionLogoutHandler
. The original handler was calledafter 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 sectionof 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
deprecated. The
$commandName
constructor argument will be removed in 3.0.v2.1.2
Compare Source
v2.1.1
Compare Source
noop
clientv2.1.0
Compare Source
Added
Individual rules in the
cache_control
can now again have amatch_response
or
additional_response_status
configuration to limit the rule to certainresponses.
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 globalcacheable
configuration is now respected to decide whether cache headersshould 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
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
Proxy client
now configured under
http
andservers
must be a list - a comma separatedstring of server IPs is no longer supported.
Event listeners
UserContextListener
constructor signature was changed totake an array of options.
XyzListener
.Rule matcher
BC break: The
match_response
andadditional_cacheable_status
configuration parameters were removed for individual match rules.
Note that
match_response
andadditional_response_status
have been re-added forcache_control
in 2.0.1.BC break: The second argument of the
RuleMatcher
constructor was changedto take a
ResponseMatcherInterface
.Cacheable status codes are now configured globally
(
cacheable.response.additional_status
orcacheable.response.expression
).Tags
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. Fortagging responses, use
fos_http_cache.http.symfony_response_tagger
instead,and to invalidate tags use the service
fos_http_cache.cache_manager
.tags.header
has been removed. Configuringthe 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
services
fos_http_cache.test.client.varnish
andfos_http_cache.test.client.nginx
no longer exist.User context
always_vary_on_context_hash
to make it possible to disableautomatically setting the vary headers for the user hash.
v1.3.16
Compare Source
v1.3.15
Compare Source
v1.3.14
Compare Source
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
tofalse rather than omit the Cookie header from
user_identifier_headers
.v1.3.12
Compare Source
v1.3.11
Compare Source
v1.3.10
Compare Source
v1.3.9
Compare Source
v1.3.8
Compare Source
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.
This PR has been generated by WhiteSource Renovate. View repository job log here.