fix(Session): Stockage des sessions côté serveur #1270
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Quoi ?
Changement de la façon de stocker les sessions.
Pourquoi ?
Le stockage de session dans le cookie (
signed_cookies) semble être la source de multiples erreurs:Les limitations de
signed_cookiessont désormais décrite ici.Comment ?
En changeant le
SESSION_ENGINEau profit decached_db. Les écritures de sessions sont appliquées à la fois au cache et à la base de données et les lectures de sessions utilisent d’abord le cache.Autre
L'activation du cache pour la session est soumis à la variable d'environnement
REDIS_CACHE_ENABLED. Si elle n'est pas fournit, les sessions sont stockées uniquement en base de données (comportement par défaut de Django).