mod_wsgi and PATH_INFO mangling
|Reported by:||Christian Boos||Owned by:||Christian Boos|
I've upgraded one of my servers from mod_python (3.3.1) to mod_wsgi (3.3), and this broke the browsing of the default repository.
This squashing doesn't play nicely with a number of our assumptions.
The first one is when building the SCRIPT_NAME from the SCRIPT_URL (r4718:4719). If this breaks, the consequences are severe as all the generated links end up broken but fortunately this seems easy to fix (patch follows).
The other problem is the autoexpand feature (#7074), where we need a similar fix.
An alternative approach would be to ensure we have no repeated "/" in our generated links, which would be a bit of a shame, as it seems to be perfectly valid to have a semantic associated with empty segments (web-sig, rfc:3875#section-4.1.5). The argument that Apache 2.x does this normalization is surprising, as this was not an issue with mod_python.
Change History (15)
by , 13 years ago
comment:1 by , 13 years ago
|Summary:||mod_wsgi issue PATH_INFO mangling → mod_wsgi and PATH_INFO mangling|