diff options
| author | Theofilos Alexiou <2019342a@users.noreply.github.com> | 2022-02-02 20:45:37 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-02-02 20:45:37 +0100 |
| commit | 3ba60951fcbc8fca3e71d3b78083b100491fa7f9 (patch) | |
| tree | 7f531cc55e9f5c2fa258214c5643cca01141fc51 | |
| parent | 84418ba3e3e42289fc31746523dfcb5e0cce5a28 (diff) | |
Added Redis to warning about using cached sessions in docs.
| -rw-r--r-- | docs/topics/http/sessions.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/topics/http/sessions.txt b/docs/topics/http/sessions.txt index 2f9f29b84b..c36554f22c 100644 --- a/docs/topics/http/sessions.txt +++ b/docs/topics/http/sessions.txt @@ -60,11 +60,11 @@ sure you've configured your cache; see the :doc:`cache documentation .. warning:: - You should only use cache-based sessions if you're using the Memcached - cache backend. The local-memory cache backend doesn't retain data long - enough to be a good choice, and it'll be faster to use file or database - sessions directly instead of sending everything through the file or - database cache backends. Additionally, the local-memory cache backend is + You should only use cache-based sessions if you're using the Memcached or + Redis cache backend. The local-memory cache backend doesn't retain data + long enough to be a good choice, and it'll be faster to use file or + database sessions directly instead of sending everything through the file + or database cache backends. Additionally, the local-memory cache backend is NOT multi-process safe, therefore probably not a good choice for production environments. |