Opened 16 years ago
Closed 15 years ago
#8650 closed (duplicate)
request.path_info is not documented
| Reported by: | dc | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | yes |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
HttpRequest.path_info is documented nowhere.
I think documentation with note that user code in most cases must use request.path_info and not request.path (for portability) is important.
Also all SCRIPT_NAME/PATH_INFO thing needs more space in documentation, not only small section in deployment.
Change History (3)
comment:1 by , 16 years ago
| Needs documentation: | set |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 16 years ago
comment:3 by , 15 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Closing in favour of #10328 which includes documentation update.
Note:
See TracTickets
for help on using tickets.
Note that most user code should *not* use
request.path_info. The only case when it should be used is if the code deals directly with url resolving.