#24468: signed_cookies backend crashes when switching from JSONSerializer to
PickleSerializer
-------------------------------------+-------------------------------------
     Reporter:  Drife59              |                    Owner:  timgraham
         Type:                       |                   Status:  assigned
  Cleanup/optimization               |
    Component:  contrib.sessions     |                  Version:  1.7
     Severity:  Normal               |               Resolution:
     Keywords:  PickleSerializer     |             Triage Stage:  Accepted
  signed_cookies                     |
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by timgraham):

 * status:  new => assigned
 * component:  Uncategorized => contrib.sessions
 * owner:  nobody => timgraham
 * has_patch:  0 => 1
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I think you had an existing session created with the `JSONSerializer` and
 are trying to load it with `PickleSerializer`. We can modify the signed
 cookies backend to silently create a new session in this case. This is
 similar to the behavior of other backends.

 [https://github.com/django/django/pull/4299 PR]

--
Ticket URL: <https://code.djangoproject.com/ticket/24468#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.b93502c665001d002178232cd21cf2e3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to