mirror of
https://github.com/django/django.git
synced 2025-07-24 13:44:32 +00:00
Fixed #14281 -- A few documentation fixes. Thanks, Ramiro and Timo.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@13964 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
136bf00615
commit
e77f16144b
6 changed files with 21 additions and 10 deletions
|
@ -939,9 +939,9 @@ Normally, you should always use :func:`~django.core.urlresolvers.reverse` or
|
|||
However, if your application constructs part of the URL hierarchy itself, you
|
||||
may occasionally need to generate URLs. In that case, you need to be able to
|
||||
find the base URL of the Django project within its web server
|
||||
(normally, :func:`~django.core.urlresolvers.reverse` takes care of this for
|
||||
(normally, :func:`~django.core.urlresolvers.reverse` takes care of this for
|
||||
you). In that case, you can call ``get_script_prefix()``, which will return the
|
||||
script prefix portion of the URL for your Django project. If your Django
|
||||
project is at the root of its webserver, this is always ``"/"``, but it can be
|
||||
changed, for instance by using ``django.root`` (see :ref:`How to use
|
||||
Django with Apache and mod_python <howto-deployment-modpython>`).
|
||||
changed, for instance by using ``django.root`` (see :doc:`How to use
|
||||
Django with Apache and mod_python </howto/deployment/modpython>`).
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue