Hi, Whether it's a bug or not, it's definitely a strange thing going on, and at this point in time I suspect the mod_jk.so is the problem. I hope I can get a little verification.
I have a <Location> Apache directive inside a SSL-enabled virtualhost, and if I go to a *directory* under that location that happens to be served by Tomcat, the URL rewrite gets munged. For example: -------- Begin sample Apache conf -------- <VirtualHost _default_:443> # General setup for the virtual host DocumentRoot "/test/html/mysite-ssl" ServerName foo.bar.com:443 ServerAdmin [EMAIL PROTECTED] ErrorLog logs/ssl_error_log TransferLog logs/ssl_access_log # SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on [... (extra config removed)] <Location /my-open-web-context> Order Allow,Deny Allow from all Satisfy any </Location> # Require authn for rest of virt host... </VirtualHost> [...] JkMount /my-open-web-context ajp13 JkMount /my-open-web-context/* ajp13 -------- End sample Apache conf -------- IF I go to https://foo.bar.com/my-open-web-context/index.jsp it works FINE. BUT if I go to https://foo.bar.com/my-open-web-context/ (i.e. no "index.jsp") I get a URL like this in my browser: http://foo.bar.com:443/my-open-web-context/index.jsp This URL of course fails because the "http" on the https port. Is this really a bug? This all worked fine with Apache 1.3. Also note that any dir handled by mod_jk NOT under the <Location> works fine. Smells like a bug. Could it be Apache itself? Should I just use jk2? There is pain between my ears. Info: Red Hat 8.0 / Apache 2.0.40, Tomcat 4.0.6LE, mod_jk.so compiled from jakarta-tomcat-connectors-jk-1.2.1-src package. Thanks for any pointers, -Dan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
