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.
What?
Added app configuration option to enable/disable saving anonymous user sessions.
Why?
Feature adds more control to a developer over behavior of session based cookies. Whether for performance (ex. bloating session storage with anonymous user sessions) or for regulatory reasons (ex. GDPR and allowing cookies), a developer can now choose to set a session based cookie when required (ex. after authenticating).
How?:
If disabled - no session is set when request arrives, instead, function access to SessionManager is provided through req->setSessionManager() and then req->setSession polymorphism will work. req-setSession() returns boolean if SessionManagerPtr is available since it might not be if config enable_session is false. We may also just call req-session() and if SessionPtr is not available it will try to setSession using the SessionManager.
Testing?
Anything Else?