Bug 52710 - mod_fcgid should set PATH_INFO when configured in 'virtual' mode
Summary: mod_fcgid should set PATH_INFO when configured in 'virtual' mode
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_fcgid (show other bugs)
Version: 2.2.16
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2012-02-19 20:42 UTC by Eugene Crosser
Modified: 2018-11-07 21:09 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Crosser 2012-02-19 20:42:04 UTC
module version 2.3.6.
When you run FcgidWrapper with 'virtual' flag (because the application has its own URL namespace), the module does not set PATH_INFO and PATH_TRANSLATED, but instead set SCRIPT_NAME and SCRIPT_FILENAME in accordance with the URL from the HTTP request. The application usually wants to see the URL in the PATH_INFO environment variable. In addition to that, I could argue that setting SCRIPT_NAME from the URL is conceptually wrong.

I think that when the wrapper is specified with 'virtual' flag, the module must provide PATH_INFO and PATH_TRANSLATED. Providing SCRIPT_NAME and SCRIPT_FILENAME is superfluous and can be dropped (but it does no harm if it's present).
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:34 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.