#32175: FORCE_SCRIPT_NAME documentation doesn't explain how the prefix is
prepended
with regard to relative vs. absolute paths.
-------------------------------+----------------------------------------
Reporter: Mason Egger | Owner: Nayan sharma
Type: Uncategorized | Status: closed
Component: Documentation | Version: 3.1
Severity: Normal | Resolution: invalid
Keywords: documentation | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+----------------------------------------
Changes (by Mariusz Felisiak):
* status: assigned => closed
* resolution: => invalid
Comment:
This behavior is already documented in
[https://docs.djangoproject.com/en/3.1/ref/settings/#media-url MEDIA_URL]
and [https://docs.djangoproject.com/en/3.1/ref/settings/#static-url
STATIC_URL] docs and it's not related with `FORCE_SCRIPT_NAME`, which is
only a way to override the server-provided value of `SCRIPT_NAME`.
--
Ticket URL: <https://code.djangoproject.com/ticket/32175#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.da02210f0309cdaf31bf612da914f2ea%40djangoproject.com.
