-
Notifications
You must be signed in to change notification settings - Fork 0
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
Server-side HTTP session configuration #22
Comments
markhobson
changed the title
Server side session configuration
Server-side HTTP session configuration
Oct 12, 2023
markhobson
added a commit
that referenced
this issue
May 23, 2024
Switches from Flask's default client-side cookie-based HTTP session to Flask-Session's SQLAlchemy storage backend. Caveat: Works fine with PostgreSQL, but intermittent SQLAlchemy errors with SQLite. Needs more work but important to ship now.
markhobson
added a commit
that referenced
this issue
May 30, 2024
Aside from the performance benefits, updating the current session's expiry date in SQLite for simultaneous requests causes a concurrency issue writing to the database.
markhobson
added a commit
that referenced
this issue
May 30, 2024
markhobson
added a commit
that referenced
this issue
May 30, 2024
markhobson
added a commit
that referenced
this issue
May 30, 2024
markhobson
added a commit
that referenced
this issue
Jun 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Migrating to server side sessions was complicated by Cloud Run behaviours (4924f09).
In our initial configuration we used a filesystem backend for Flask-Session to manage server side sessions. However in Cloud Run the compute resources time out quickly meanining that the filesystem session data is lost and leading to internal server errors. For now these changes have been revoked but in future we'd like to return to this, potentially looking at an alternate backend (https://flask-session.readthedocs.io/en/latest/interfaces.html).
The text was updated successfully, but these errors were encountered: