This repository was archived by the owner on Dec 12, 2023. It is now read-only.
Add saveUninitialized option #41
Open
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.
Forces a session that is "uninitialized" to be saved to the store. A session is uninitialized when it is new but not modified. Choosing
falseis useful for implementing login sessions, reducing server storage usage, or complying with laws that require permission before setting a cookie.The default is
true, as it has been before, so it shouldn't affect the current behavior of the middleware. The option should behave similar to the saveUninitialized option inexpress-session.Implementing this has been a bit tricky. The idea was to get a listener to the
event.context.sessionserver object, which creates a session when the object has been modified and therefore sends a cookie to the client. I'm not aware of any listener which gets called when every event handler is finished, so I built a proxy for theres.end()method to get a hook to the very end of all event listeners.The proxy is only in use when setting
saveUninitialized = false.