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
bug #49745 [FrameworkBundle] Fix wiring session.handler when handler_id is null (nicolas-grekas)
This PR was merged into the 5.4 branch.
Discussion
----------
[FrameworkBundle] Fix wiring session.handler when handler_id is null
| Q | A
| ------------- | ---
| Branch? | 5.4
| Bug fix? | yes
| New feature? | no
| Deprecations? | no
| Tickets | -
| License | MIT
| Doc PR | -
When the session `handler_id` is null, we currently set the `$handler` argument of the storage/factory services to null, which means to them "create your own handler internally from the native one". This means that the `session.handler` service is "a lie": it's not the real handler used by the storage. It also means that the `%session.save_path%` parameter is lying too, because it is set to `%kernel.cache_dir%/sessions` (by default), while the storage will use `ini_get('session.save_path')` in practice.
This issue is 10 years old... #5290
Commits
-------
e23be58348 [FrameworkBundle] Fix wiring session.handler when handler_id is null
0 commit comments