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=28173>. 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=28173 Customizable error responses don't work the way they are intended to ------- Additional Comments From [EMAIL PROTECTED] 2004-04-04 15:12 ------- I'm glad to be able to confirm that this is NOT an issue, after having thoroughly tested all possible situations I could think of. Even in case of involving virtual hosts. Unless one places the 'Alias /error/include/ "..."' directive after the 'Alias /error/ "..."' directive I cannot repeat any previous problems. Although the SSI related problems occured due to having moved 'error/include' to 'error-include' (i.e. to the same level as 'error'), at the same time as having defined 'Alias /error/include/ "/usr/local/apache2/error-include/"' but having put it AFTER 'Alias /error/ ...'. Because 'Alias /error/include/ ...' in this case is ignored, SSI - of course - couldn't find the files residing in the 'include' sub-directory of directory 'error'. I have no explanation to why I still got the same error after having moved the 'Alias /error/include/ ...' directive BEFORE the 'Alias /error/ ...' directive, other than having forgotten to restart the server or having forgotten to clear my browsers cache. Anyway, that doesn't matter. The important thing is that it works. Thus I have to do a "pudel", and appologize for the doubts my false alarm may have caused. Kind Regards, Rolf Sponsel BTW, Yes I think it might be good to point this out in the documentation/httpd-std.conf file, unless this is not the default behaviour when using the 'Alias' directive. I couldn't find that information in the Apache2 documentation. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
