Opened 10 years ago
Closed 10 years ago
#24450 closed Uncategorized (needsinfo)
Should the WSGI Core handler accept request with a missing slash '/'
| Reported by: | paschembri | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (URLs) | Version: | 1.7 |
| Severity: | Normal | Keywords: | wsgi nginx script_name |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I observed that when using nginx with gunicorn and the SCRIPT_NAME is set to '/' every request is stripped from the leading '/'.
The consequence is that these requests cannot be correctly resolved.
As documented, when path_info is empty, it is graciously forced to '/'. But when path_info does not start with '/', nothing is done.
Is this behavior desirable ?
Change History (2)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
| Resolution: | → needsinfo |
|---|---|
| Status: | new → closed |
Please reopen if you can follow up with more details. Thanks.
Note:
See TracTickets
for help on using tickets.
Hi, could you add a little more detail about the steps to reproduce the issue and also a pointer to the documentation you refer to in your third paragraph?