#25435: Add support for request.urlconf to CurrentSiteMiddleware
-------------------------------+---------------------
Reporter: ngnpope | Owner: ngnpope
Type: New feature | Status: new
Component: contrib.sites | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+---------------------
There are a number of situations in which it would be useful to be able to
configure `request.urlconf` on a per-site basis. In some cases we may have
separate sites using the same code base but a different structure of URLs
or serving up different content, e.g. a REST API. I have also had to cater
for a situation where I needed another version of a site on a different
sub-domain with access to a restricted set of URLs that the main site
provides.
I have been using the sites framework and propose the addition of a
`urlconf` field to `Site` such that the `CurrentSiteMiddleware` can use
`request.site.urlconf` to set `request.urlconf`. This also has the benefit
that accessing the site with different `Host` headers can result in
serving up the different URLconf automatically based on the site that was
accessed.
--
Ticket URL: <https://code.djangoproject.com/ticket/25435>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.f1033f2f9d5ebf556288a1b49efabbdb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
