#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 |
----------------------------------------------------------------+-----------
Comment (by lukeplant):
Replying to [comment:13 anonymous]:
> Does the patch in #9977 provide for a 403.html template for
PermissionDenied errors?
No, it doesn't. I guess if you removed the CSRF stuff from the patch,
this would be useful in its own right, and the bug title would probably
want to change. A problem I have with the patch, on top of the concerns
Jacob raised, is the issue of i18n — if we want to solve this, we want to
do it right.
--
Ticket URL: <http://code.djangoproject.com/ticket/5515#comment:14>
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
-~----------~----~----~----~------~----~------~--~---
