Opened 16 years ago
Closed 16 years ago
#7191 closed (fixed)
URL dispatcher page, small error
Reported by: | anonymous | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Mistake on this page:
http://www.djangoproject.com/documentation/url_dispatch/
Quote (from section "What the URLconf searches against"):
For example, in a request to http://www.example.com/myapp/, the URLconf will look for /myapp/. In a request to http://www.example.com/myapp/?page=3, the URLconf will look for /myapp/.
I don't think there should be a leading slash on each of those two occurrences of "/myapp/".
(The Django book in chapter 8 has a very similar pair of statements but doesn't include leading slashes, so that book is correct.)
Attachments (1)
Change History (4)
comment:1 by , 16 years ago
Triage Stage: | Unreviewed → Accepted |
---|
by , 16 years ago
Attachment: | url_dispatch.patch added |
---|
comment:2 by , 16 years ago
Has patch: | set |
---|---|
Triage Stage: | Accepted → Ready for checkin |
comment:3 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [7560]) Fixed #7191 -- Removed leading slashes in description of the patterns that a URLconf checks when GET data is present. Thanks, andrews.