#5515: Custom Permission Denied Pages
----------------------------------------------------------------+-----------
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 fvox13):
* status: reopened => closed
* resolution: => duplicate
Comment:
The CSRF handling has changed substantially in 1.2, and there are indeed
benefits to having separate handling for the 403s raised by CSRF. "You
need cookies and you need to stop mucking with the token you l33t hax0r
d00d" is different than "you can't access that foo because permission is
denied". #9847 covers the second use case, so let's continue this
discussion there.
--
Ticket URL: <http://code.djangoproject.com/ticket/5515#comment:20>
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.
