PATH_INFO incorrect

Bug #142655 reported by Bug Importer
0
Affects Status Importance Assigned to Milestone
Zope 2
Invalid
Medium
Unassigned

Bug Description

according to http://hoohoo.ncsa.uiuc.edu/cgi/env.html, PATH_INFO should
contain the data after the script path. Like:
http://server/cgi-bin/script/some/more/data should lead to
PATH_INFO=/some/more/data
PATH_INFO should be empty or undefined otherwise (both Apache and
thttpd have it undefined).

Zope has it set to the path of the script instead.

Tags: bug zope
Revision history for this message
ken manheimer (ken-manheimer) wrote :

This is a test to see if anyone is able to followup on an issue - toni tells me he's getting some kind of error when he tries.

Revision history for this message
Hanno Schlichting (hannosch) wrote :

Zope considers everything after the traversal root to be the "script path". We won't change this anymore today.

Changed in zope2:
status: New → Won't Fix
Revision history for this message
Tres Seaver (tseaver) wrote :

The correct model for this is to consider the Zope application itself as analogous to a CGI script, rather than any given PythonScript object hosted inside the ZODB: PATH_INFO is information which the server passes to the application, just as with Apache and CGI, representing the "rest" of the path. It is arguable that Zope should adjust SCRIPT_NAME and PATH_INFO when doing virtual hosting, to make the "virtual root" function as the "base" object: that might still happen under WSGI when we finish fixing it.

Changed in zope2:
status: Won't Fix → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.