From 698c8dfc2a5c5865a8bb163c1ae70b75d53e6415 Mon Sep 17 00:00:00 2001 From: Berker Peksag Date: Tue, 31 May 2016 04:21:00 -0700 Subject: [PATCH] Fixed #26503 -- Removed an outdated example from session docs. --- docs/topics/http/sessions.txt | 9 --------- 1 file changed, 9 deletions(-) diff --git a/docs/topics/http/sessions.txt b/docs/topics/http/sessions.txt index aa3a3cf704..6e2b48be86 100644 --- a/docs/topics/http/sessions.txt +++ b/docs/topics/http/sessions.txt @@ -492,15 +492,6 @@ An API is available to manipulate session data outside of a view:: >>> s['last_login'] 1376587691 -In order to mitigate session fixation attacks, sessions keys that don't exist -are regenerated:: - - >>> from django.contrib.sessions.backends.db import SessionStore - >>> s = SessionStore(session_key='no-such-session-here') - >>> s.save() - >>> s.session_key - 'ff882814010ccbc3c870523934fee5a2' - If you're using the ``django.contrib.sessions.backends.db`` backend, each session is just a normal Django model. The ``Session`` model is defined in ``django/contrib/sessions/models.py``. Because it's a normal model, you can