DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10489>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10489 SSI is inconsistent Summary: SSI is inconsistent Product: Apache httpd-2.0 Version: 2.0.39 Platform: Sun OS/Version: Solaris Status: NEW Severity: Normal Priority: Other Component: Other Modules AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] hello I have been in the process of upgrading my test instance of apache from 1.X to the current 2.0.39 release, before doing the production instance. I think I have found an inconsistent behaviour with server side includes and the 2.0.39 release (and likely earlier versions of 2.XX). I have posted the problem on comp.infosystems.www.servers.unix and got no replies. I dont believe that the problem is a configuration issue (in as much as I have been trying to start with my older config settings etc. where SSI works fine, and using them with the new config settings for the 2.0.39 release). I have it set up to parse all htm pages, since they all contain headers and footers referenced via includes. I can get ssi working fine for all html documents in my document root tree, EXCEPT for a document named index.htm at root of the tree. If I copy /index.htm to /index2.htm (or any other name) the SSI directives are processed, but not if the file is titled index.htm at root. If I copy index.htm down to a subdirectory, SSI directives get processed there as well just fine. It just is not parsing the includes at the root level for that single file called index.htm relevant portions of my new httpd.conf file are: <Directory "/wwwadmin/test_web_docs"> Options Includes FollowSymLinks SetOutputFilter INCLUDES AllowOverride None order allow,deny allow from XXX deny from * </Directory> and later on.... AddType text/html .html AddType text/html .htm AddOutputFilter INCLUDES .htm Could this effect be due to conflict or processing being intercepted by another module? Thanks in advance for looking at this. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
