#5515: CSRF has hard-encoded error page
----------------------------------------------------------------+-----------
Reporter: Piotr Lewandowski <[email protected]> |
Owner:
Status: closed |
Milestone:
Component: Contrib apps |
Version: SVN
Resolution: duplicate |
Keywords:
Stage: Design decision needed |
Has_patch: 1
Needs_docs: 0 |
Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------------------------------+-----------
Changes (by lukeplant):
* status: new => closed
* resolution: => duplicate
Comment:
The patch in #9977 addresses this issue by allowing the user to provide
their own view function for the CSRF failure view. This is more useful
than just a template, as the view can do logic based on the contents of
the request. So I'm closing as duplicate, since the other patch, which
includes big changes to the CSRF functionality, is very likely to go in
post 1.1
--
Ticket URL: <http://code.djangoproject.com/ticket/5515#comment:12>
Django <http://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
-~----------~----~----~----~------~----~------~--~---
