URLs will be processed in the order they appear in your urls.py file. If one of your first entries in urls.py is an "include" that handles all URLs that start with "/a/", then all those requests will be handled by the URL patterns in the included URLs.py.
Then, all URLs that don't get "caught" by that pattern will be checked against the rest of the patterns in your urls.py until it finds a match. According to the docs[1], urls.py has no access to the domain in question, so this is a bit of a workaround. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAOzwKwECOUrPmPyZLSSexozaMq2QS7nFW1e1z1Ejyf%2B%2BxdpqFg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
