-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Sessions and expressSequelizeSession #1668
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
same issue. did you happen to find the reason @danmmx ? |
It might be the same as our issue 1597. This is becoming a problem, since the storage quota gets filled quite fast. |
I didn't @saurabhverma2892 . And probably the same issue @andershagebakken . |
temporary solution: comment out everything related to sessions and lusca in /server/config/express.js.
|
That express middleware seems to be unmaintained. Has anyone tried connect-session-sequelize ? |
What can I use for Mongoose? |
@andershagebakken When you scaffold with the Mongo option, it will use |
Okay. Thanks. But how can I fix the issue of the growing sessions collection as described in 1597, similar to this issue? |
@andershagebakken @Awk34 I think this issue is upstream with |
I don't know yet. I haven't had any time to investigate it. As @saurabhverma2892 said, if you just comment out all of the session-related code the problem goes away (obviously). The two things that rely on sessions are Lusca (for security purposes) and Twitter OAuth (OAuth 1). |
@mhheise Yes! If you can confirm that that works, PRs are always welcome! Also, you might want to test out connect-session-sequelize instead of express-sequelize-session, since the former seems to be more maintained. |
@andershagebakken The reason for sessions is explained here as well. I've never used Helmet, but of course you can try anything you'd like! Lusca is just provided as the default for convenience's sake. |
@Awk34 Absolutely! I will work on a PR at least for the fix with the current session packages and I can also test the |
@mhheise awesome. Since it's a fix, make sure to branch from the 'master' branch if you get things working |
Fixes an upstream issue in express-session or express-sequelize-session where static middleware requests: - Hit the session store, - Overwrite one another, and - Generate many new sessions. Fixes #1668.
I just generated a project and just running it with
logging: on
from Sequelize I get tons of queries on theSessions
table.^ All of this on a single reload on the home page
The text was updated successfully, but these errors were encountered: