>Number: 5800 >Category: mod_actions >Synopsis: PATH_INFO/PATH_TRANSLATED are incorrect when used with >Action/AddHandler >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Tue Feb 22 14:20:00 PST 2000 >Closed-Date: >Last-Modified: >Originator: [EMAIL PROTECTED] >Release: 1.3.6 >Organization: apache >Environment: win32 + unix? >Description: On 11/30/1999, Jim Garrison asked on comp.infosystems.www why does path_info exhibit such inconsistent behavior in the presence of an action directive. He set .pdq to be handled by printenv.cgi and go the following behavior: > http://host.domain.com/zzz/printenv.cgi/additional > invokes the script with PATH_INFO set as > PATH_INFO = /additional > whereas the URL > http://host.domain.com/pdq/test.pdq/additional > invokes the script with PATH_INFO set as > PATH_INFO = /pdq/test.pdq/additional > which seems to be a bug. I was expecting the same > PATH_INFO in both cases.
Even wierder is that, if test.pdq doesn't exist, apache issues a 404 rather than executing your handler. The only answer I saw was David Efflandt's: > When a CGI is invoked as an Action handler, it gets the full URL path to > the request (not including domain) as > PATH_INFO and the system path to the requested file as PATH_TRANSLATED. > Both are according to the Apache docs. So which one don't you > understand and why would you expect different URL paths to give you the > same PATH_INFO? However, under test.pdq, PATH_TRANSLATED is test.pdq/additional, a file that does not exist! Since apache won't execute the handler unless test.pdq exists, the path translated must really be /path/to/pdq/test.pdq (PATH_TRANSLATED notwithstanding). >How-To-Repeat: >Fix: Under test.pdq, Apache should do: SCRIPT_NAME = /pdq/test.pdq PATH_INFO = /additional PATH_TRANSLATED = /path/to/pdq/test.pdq >Release-Note: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]
