#16774: Backtracking URL resolver
-------------------------+-------------------------------
Reporter: nbstrite | Owner: nobody
Type: New feature | Status: new
Milestone: | Component: HTTP handling
Version: 1.3 | Severity: Normal
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Easy pickings: 0
UI/UX: 0 |
-------------------------+-------------------------------
Right now the URL resolver only resolves to the first matched URL, and the
view that is resolved to is unable to inspect the requested URL to see if
it truly should be the view to be handling this URL. You can only have one
"catch all" url pattern, however, occasionally it would make sense to
allow distinct applications to receive a URL and upon inspection claim it,
or allow the URL resolver to continue to find a match (i.e. CMS, legacy
database driven system to handle legacy urls, etc.)
https://github.com/django/django/pull/37
Thoughts?
If this is a desired feature, then I would be happy to write the docs or
further this concept.
Thanks!
Nowell Strite
--
Ticket URL: <https://code.djangoproject.com/ticket/16774>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
