#25598: support for SCRIPT_NAME for static tag and FileField.url
-------------------------------------+-------------------------------------
Reporter: DheerendraRathor | Owner: nobody
Type: New feature | Status: new
Component: Uncategorized | Version: master
Severity: Normal | Resolution:
Keywords: script_name, | Triage Stage:
static_url, media_url | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by claudep):
I think that the idea basically makes sense. Ideally, a Django instance
shouldn't need to know at which subpath it is being deployed, as this can
be considered as purely sysadmin stuff. It would be a good separation of
concerns. For example, the Web administrator may change the
WSGIScriptAlias from /foo to /bar and the application should continue
working. Of course, this only applies when *_URL settings are not full
URIs.
In practice, it's very likely that many running instances are adapting
their *_URL settings to include the base script path, hence the behavior
change would be backwards incompatible. The question is whether the change
is worth the incompatibility.
--
Ticket URL: <https://code.djangoproject.com/ticket/25598#comment:4>
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/074.dd8e05c97fd0e3e732a70ed551b33ca9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
