#25435: Add support for request.urlconf to CurrentSiteMiddleware
-------------------------------+--------------------------------------
Reporter: ngnpope | Owner: ngnpope
Type: New feature | Status: closed
Component: contrib.sites | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by claudep):
* status: new => closed
* resolution: => wontfix
Comment:
I don't think that your use case is general enough to warrant a new field
in the Site model. This looks like a very deployment-specific situation.
As for me, the "Djangonic" way of achieving this is to have a combination
of settings and your own middleware to do the clever urlconf
configuration.
Feel free to discuss that on the [https://groups.google.com/forum/#!forum
/django-developers django-developers] mailing list if you disagree.
--
Ticket URL: <https://code.djangoproject.com/ticket/25435#comment:2>
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/065.2e155d700f72a459d3edaecf69c82be2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
