You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/12/01 10:57:06 UTC

DO NOT REPLY [Bug 25104] New: - (Apache 2.0.x) mod_jk 1.2.5 ignores -ForwardDirectories

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=25104>.
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=25104

(Apache 2.0.x) mod_jk 1.2.5 ignores -ForwardDirectories

           Summary: (Apache 2.0.x) mod_jk 1.2.5 ignores -ForwardDirectories
           Product: Tomcat 4
           Version: 4.1.29
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Connector:JK/AJP (deprecated)
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: hannumk@sunpoint.net


Using Apache 2.0.48, Tomcat 4.1.29 and mod_jk 1.2.5 on Solaris.

All HTTP-requests for directories without index.html
get served by Tomcat even if "JkOptions -ForwardDirectories"
is used (or ForwardDirectories is removed).

Apache has no "Options Indexes" set, so requests
to directories without a proper index file should
be rejected with a "403 Forbidden". Directories
containing index.html should be served by Apache
whereas only requests for directories with index.jsp
should be directed to Tomcat via mod_jk.

DocumentRoot in Apache and appBase in Tomcat
point to same directory.


Steps to Reproduce:

1.) Relevate settings from httpd.conf:
 ...
 DirectoryIndex index.html index.jsp
 ...
 <IfModule mod_jk.c>
   JkWorkersFile /confdir/workers.properties
   JkLogFile /logdir/mod_jk.log
   JkLogLevel info
   JkLogStampFormat "[%d.%m.%Y %H:%M:%S] "
   JkOptions -ForwardDirectories
   JkMount /*.jsp ajp13
 </IfModule>

2.) Create a test directory ("/fortomcat") with
    simple index.jsp within and an empty directory
    ("/notfortomcat") as well.

3.) Make HTTP-requests for both directories.


Expected Results:

 http://host/fortomcat/
 -> 200 OK (Tomcat serving index.jsp) or
    500 Internal Server Error (Tomcat complaining
    about "No context configured...")
 
 http://host/notfortomcat/
 -> 403 Forbidden (error from Apache)


Actual Results:

 http://host/fortomcat/
 -> 200 OK (Tomcat serving index.jsp) or
    500 Internal Server Error (Tomcat complaining
    about "No context configured...")
 
 http://host/notfortomcat/
 -> 500 Internal Server Error (Tomcat complaining
    about "No context configured...") WRONG!


Additional Information:

ForwardDirectories was broken in mod_jk 1.2.4 too.
With 1.2.4, requests for directories where never
forwarded to Tomcat ("JkOptions +ForwardDirectories"
did not work). This was "fixed" in 1.2.5:

Changes with JK 1.2.5
    * Fix Apache 2 connector so that DirectoryIndex works for an
      index.jsp page if JkOptions ForwardDirectories was configured.
      [hgomez]

Now forwarding works a bit too well. :)

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org