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=41430>. 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=41430 Summary: JkOptions +ForwardDirectories with Apache's DirectoryIndex Product: Tomcat 5 Version: 5.5.0 Platform: PC OS/Version: Linux Status: NEW Severity: regression Priority: P2 Component: Native:JK AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] In apache-2.0.58 + apr-0.9.12 + mod_jk-1.1.20 + JBoss-4.0.5.GA (Tomcat 5.5), when a Tomcat webapp is published through an apache vhost and: - both JkOptions +ForwardDirectories and DirectoryIndex are specified; - Apache can't stat() the specified index file, since it is expected to be handled virtually by Tomcat (i.e.: it is "index.jsf" like in Java ServletFaces applications); then issuing a request on a directory entry to Apache (like, in example, http://www.domain.tld/) would not redirect the client to request the DirectoryIndex-specified resource (i.e. http://www.domain.tld/index.jsf) but would instead forward it up to Tomcat as-is. This results in displaing the directory content (or a 404 error), instead of the wanted index virtual file. Please note that up to mod_jk-1.1.19 the behaviour I was seing was the expected one: the client was redirected to request the virtual index resource regardless of the existance of such a file in the directory published by Apache. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
