-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
PR #25583 and #25699 BC Break #26237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello, thank you for your report. |
@nicolas-grekas thanks for the info, i still see it somewhat as BC break, because it worked and then it broke :) But i fixed it for myself by defining all urls which need the user object in my security.yml so the cache-control will be only changed for these urls, which is fine and wanted. |
OK, all good then. Any bug fix is a BC break :) |
PR #25583 and #25699 overwrites cache-control even if i manually set them to public. This breaks compatibility. version 3.4.2 works.
I use varnish to cache and have several actions with explicit
@Cache
annotation to cache them by varnish, regardless if the user is logged in or not. This worked since 2.7 and till 3.4.2.With the PR #25583 this broke, but was relatively easy to fix by overwriting the savesession listener.
With #25699 the change got moved to the abstract class which makes it even harder to overwrite.
Probably by modifying the session object but still, in my opinion its a BC Break.
The text was updated successfully, but these errors were encountered: