You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2008/01/29 01:19:27 UTC

DO NOT REPLY [Bug 44316] New: - httpd 2.0 does not follow ScriptAliases when invoking an ErrorDocument

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44316>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=44316

           Summary: httpd 2.0 does not follow ScriptAliases when invoking an
                    ErrorDocument
           Product: Apache httpd-2
           Version: 2.2.8
          Platform: All
        OS/Version: Linux
            Status: NEW
          Keywords: ErrorMessage
          Severity: normal
          Priority: P2
         Component: Core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: phil@co.ordinate.org


The documentation for ScriptAlias states that "It is safer to avoid placing CGI
scripts under the DocumentRoot in order to avoid accidentally revealing their
source code if the configuration is ever changed. The ScriptAlias makes this
easy by mapping a URL and designating CGI scripts at the same time."

httpd 1.x would follow ScriptAliases to correctly call a CGI error handler
specified with an ErrorDocument statement, located in a ScriptAliased CGI
directory located outside the DocumentRoot as per the above advice.  httpd 2.0
does NOT follow ScriptAliases when calling an ErrorDocument, resulting in a 500
Internal Server Error.  Nothing is logged to indicate the cause of the error,
and the fact that ErrorDocument calls do not follow ScriptAliases is not
documented anywhere (that I've found, at least).
Since it is not documented that httpd 2.0 does NOT follow ScriptAliases when
invoking an ErrorDocument, and it worked in httpd 1.0, there is no reason to
suspect when troubleshooting the failure that this is the problem.  There is no
obvious way to reproduce the failure that yields any information about why it
failed.

To further confuse diagnosing the problem, if you try to test your error-handler
CGI by setting up an alias to load the CGI directly in a browser, instead of in
response to an error, the ScriptAlias will be followed, and the CGI will work
exactly as you expect it to.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org