#16768: Wrong cookie set by CSRF middleware
--------------------------------------+------------------------------
Reporter: ike@… | Owner: nobody
Type: Bug | Status: closed
Milestone: | Component: contrib.csrf
Version: 1.3 | Severity: Normal
Resolution: invalid | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------+------------------------------
Changes (by PaulM):
* status: new => closed
* needs_docs: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
That looks like the issue (that isn't going to be fixed) where cookie
objects can't be stored in pickles (and thus can't be stored in the
various caching backends). Your application is probably caching or storing
the cookie somewhere (or may be configured to cache pages which contain
cookies, which is a definite bad thing). I'm closing as invalid, but feel
free to comment or re-open if you've got clear steps to reproduce the
problem and you think it's a Django issue and not something your
application is doing.
--
Ticket URL: <https://code.djangoproject.com/ticket/16768#comment:1>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
