#28609: Original request URI is not available to development server
-------------------------------------+-------------------------------------
Reporter: Jay Lynch | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Management | Version: 1.11
commands) |
Severity: Normal | Resolution: wontfix
Keywords: server http-server | Triage Stage:
runserver | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jay Lynch):
My mistake, sorry! I hadn't realised it was all that, I assumed based on
the name it would just be an easier way to get started with mod_wsgi.
It looks quite cool. Unfortunately doesn't help much though, I don't
really want to get Apache involved when we don't use it for anything else.
It feels like an awkward middle ground, adding a third incompatible
environment - if we were going to go that far I'd rather go all the way
and use Kubernetes to actually mirror production and have universally
consistent environments. It's a while away on our current plan though, and
not a project I'm keen on pulling forward for something this minor.
--
Ticket URL: <https://code.djangoproject.com/ticket/28609#comment:7>
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/066.1e559c13c13ef86e8baf57df2a7db3ca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.