You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Symfony is using the php's header function... I expect from symfony to use always a Response object as set all the headers there.. having this exception for the session was not trivial to discover...
Can't this be done using some response listener?
In my case I also had @Cache(maxage=999)... and this was generating two Cache-Control headers...
The current session implementation sends some "Cache" headers really similar to http://php.net/manual/en/function.session-cache-limiter.php
This behavior can be configured by setting some properties into the parameter,
session.storage.options
As example:
If
cache_limiter
is0
symfony will not set any particular header header and will fallback on what specified by http://php.net/manual/en/session.configuration.php#ini.session.cache-limitercache_limiter
can also be set to one of the nocache, private, private_no_expire, or public valesRelated to symfony/symfony#24988 (comment)
As suggested here symfony/symfony#24988 (comment) should be documented that changing this value should be done carefully.
The text was updated successfully, but these errors were encountered: