Session save does not support a callback url
See original GitHub issueCookie session does not implement the documented interface for express session save
. As you can see here :
https://github.com/expressjs/session/blob/8e57b21bef0d53010c4d37f4beee3f0341f3eaa6/session/session.js#L71
and per the documentation here: https://github.com/expressjs/session#sessionsavecallback
Save should take an optional callback method. The background is i’m trying to implement this fix: https://github.com/jaredhanson/passport/issues/482#issuecomment-230594566 But I can’t since there is no callback url
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
How do I store a value in session that has to be later accessed ...
You just need to make sure that the callback request instructs the server somehow to use the same session as the initial request....
Read more >auth0 url
Auth0 will not accept the default certificate in the SAML Find top links about ... This corresponds to an Auth0 callback URL: To...
Read more >Authorizing requests - Postman Learning Center
To use authorization code grant type, enter a Callback URL for your client application (which needs to be registered with the API provider),...
Read more >AuthSession - Expo Documentation
The Expo Auth service saves away the returnUrl (and if it is not a published URL or your registered custom theme, shows a...
Read more >Window.sessionStorage - Web APIs - MDN Web Docs
The read-only sessionStorage property accesses a session Storage object for the current origin. sessionStorage is similar to localStorage; ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It probably doesn’t matter at this point, as the 1.x series is about to be deprecated with the release of 2.0.
Sorry I didn’t get to doing this. No PR came up either, and as I was about to do this, I noticed that save was never a documented method and the JSDoc marks it as a private API, so probably best just to actually remove the ability for users to call it at all from 2.0 to prevent confusion. Calling
.save()
just generates a cookie value and is a sync action, so has no purpose in this module.