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
{{ message }}
This repository has been archived by the owner on Dec 13, 2018. It is now read-only.
Right now, this library initializes its own session stuff as req.session. This is a problem for many people, as most node libraries initialize their own session stuff under the same name -- this causes issues.
What I'd like to do is migrate all Stormpath session stuff to req.stormpathSession, this way there will be no chance of conflict for non-auth related sessions.
I've got about 99% of this code ready to ship, but the CSURF library doesn't currently support anything other than req.session, which is a blocker for this.
Right now, this library initializes its own session stuff as
req.session
. This is a problem for many people, as most node libraries initialize their own session stuff under the same name -- this causes issues.What I'd like to do is migrate all Stormpath session stuff to
req.stormpathSession
, this way there will be no chance of conflict for non-auth related sessions.I've got about 99% of this code ready to ship, but the CSURF library doesn't currently support anything other than
req.session
, which is a blocker for this.I've opened a ticket on the CSURF library page: expressjs/csurf#66
If the author gives me the go ahead, I'll submit a PR to their project, and then once released, push the changes into this library.
The text was updated successfully, but these errors were encountered: