Fixed #7191 -- Removed leading slashes in description of the patterns that a URLconf checks when GET data is present. Thanks, andrews.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@7560 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
6b39dd6977
commit
812d8d40bd
|
@ -157,10 +157,10 @@ The URLconf searches against the requested URL, as a normal Python string. This
|
||||||
does not include GET or POST parameters, or the domain name.
|
does not include GET or POST parameters, or the domain name.
|
||||||
|
|
||||||
For example, in a request to ``http://www.example.com/myapp/``, the URLconf
|
For example, in a request to ``http://www.example.com/myapp/``, the URLconf
|
||||||
will look for ``/myapp/``.
|
will look for ``myapp/``.
|
||||||
|
|
||||||
In a request to ``http://www.example.com/myapp/?page=3``, the URLconf will look
|
In a request to ``http://www.example.com/myapp/?page=3``, the URLconf will look
|
||||||
for ``/myapp/``.
|
for ``myapp/``.
|
||||||
|
|
||||||
The URLconf doesn't look at the request method. In other words, all request
|
The URLconf doesn't look at the request method. In other words, all request
|
||||||
methods -- ``POST``, ``GET``, ``HEAD``, etc. -- will be routed to the same
|
methods -- ``POST``, ``GET``, ``HEAD``, etc. -- will be routed to the same
|
||||||
|
|
Loading…
Reference in New Issue