From bfcecbffd37a68b5fffe81954c17aedeacb1ba22 Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Mon, 21 Jul 2008 07:57:10 +0000 Subject: Changed/fixed the way Django handles SCRIPT_NAME and PATH_INFO (or equivalents). Basically, URL resolving will only use the PATH_INFO and the SCRIPT_NAME will be prepended by reverse() automatically. Allows for more portable development and installation. Also exposes SCRIPT_NAME in the HttpRequest instance. There are a number of cases where things don't work completely transparently, so mod_python and fastcgi users should read the relevant docs. Fixed #285, #1516, #3414. git-svn-id: http://code.djangoproject.com/svn/django/trunk@8015 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/settings.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'docs/settings.txt') diff --git a/docs/settings.txt b/docs/settings.txt index fbe23b5e88..2c9e56abd4 100644 --- a/docs/settings.txt +++ b/docs/settings.txt @@ -578,6 +578,16 @@ these paths should use Unix-style forward slashes, even on Windows. See .. _Testing Django Applications: ../testing/ +FORCE_SCRIPT_NAME +------------------ + +Default: ``None`` + +If not ``None``, this will be used as the value of the ``SCRIPT_NAME`` +environment variable in any HTTP request. This setting can be used to override +the server-provided value of ``SCRIPT_NAME``, which may be a rewritten version +of the preferred value or not supplied at all. + IGNORABLE_404_ENDS ------------------ -- cgit v1.3