mod_alias/7072: ScriptAliasMatch behavior confusing w.r.t. PATH_INFO, probably needs better doc

[Dave Dykstra <dw...@bell-labs.com>]

>Number:         7072
>Category:       mod_alias
>Synopsis:       ScriptAliasMatch behavior confusing w.r.t. PATH_INFO, probably needs better doc
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Jan 15 09:20:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     dwd@bell-labs.com
>Release:        1.3.12
>Organization:
apache
>Environment:
Redhat 6.2
>Description:
I had this ScriptAliasMatch configuration directive:
    ScriptAliasMatch (.*\.cgi) /usr/www/pages/$1
When a CGI script is invoked with an extra path component such as "tst.cgi/foo"
the SCRIPT_NAME gets set to the full path and PATH_INFO is not set.  It works
ok with "tst.cgi?foo"; that is, QUERY_STRING gets set ok.  The fix is to put a
".*" at the end of the pattern to match, like this:
    ScriptAliasMatch (.*\.cgi.*) /usr/www/pages/$1
>How-To-Repeat:

>Fix:
I suggest that the ScriptAliasMatch keyword documentation be expanded to help
people avoid this error (assuming you don't want to change the behavior of
ScriptAliasMatch, although you may want to).  Perhaps all it will take is a
second example in addition to the cgi-bin example.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> 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!     ]