This repository has been archived by the owner on Jan 31, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 64
Lazy session start #43
Comments
I've the same problem on my application. Do you have any idea how to resolve this problem properly ? |
Containers should not be injected, but rather requested at runtime. Session containers are NOT services. |
This repository has been closed and moved to laminas/laminas-session; a new issue has been opened at laminas/laminas-session#21. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The current container object starts a session in the constructor automatically. This works fine for most use cases, but it could come in handy to use some kind of delayed session start. I'm working on a REST API which accepts API keys, but also check for authenticated users in their sessions. The authentication for the users are stored in sessions. However, every API call from a REST client generates a session. It will send a cookie to the REST client, while also storing the session information on disk. This should not happen with every API call by REST clients.
It would be great to have a container which does not automatically starts a session, only under the following circumstances:
session_status
returnPHP_SESSION_NONE
and$_COOKIE[session_name()]
is set. This will only start a session when the browser actually has send a cookie to the server.The text was updated successfully, but these errors were encountered: