#15607: Custom error templates in a single Django application
-----------------------------------------+----------------------
Reporter: jose | Owner: nobody
Status: closed | Milestone:
Component: HTTP handling | Version: 1.2
Resolution: needsinfo | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
-----------------------------------------+----------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => needsinfo
* needs_tests: => 0
* needs_docs: => 0
Comment:
It's not entirely clear to me what is being proposed here. At a high
level, having multiple handlers for 404 and 500 errors sounds like a
reasonable idea, but I'm not sure how this would be interpreted in
practice.
In particular -- what delineates the "app" boundary that decides which
error page is used? An "App" isn't something that has a clear boundary --
it's just a collection of views. Consider the following pathological, but
entirely legal case:
{{{
urlpatterns = patterns('',
(r'^foo/', include('app1.urls')),
(r'^foo/', include('app2.urls')),
)
}}}
How do you define a custom 404/500 handler for 'app1', and under what
circumstances is it invoked?
--
Ticket URL: <http://code.djangoproject.com/ticket/15607#comment:1>
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.
