diff options
| author | Theofilos Alexiou <2019342a@users.noreply.github.com> | 2022-02-02 20:45:37 +0100 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2022-02-02 20:46:44 +0100 |
| commit | efe72cf128a37cd11ba28fde6ed82e73be4f90d2 (patch) | |
| tree | 766d59125f407db6b58f8e37ad273b3ebba9917b /docs | |
| parent | 7043f9ab3f151c9777b0ef660fa4386c4d53dad7 (diff) | |
[4.0.x] Added Redis to warning about using cached sessions in docs.
Backport of 3ba60951fcbc8fca3e71d3b78083b100491fa7f9 from main
Diffstat (limited to '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 34dabdd536..1837ff1c6d 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. |