aspose file tools*
The moose likes Tomcat and the fly likes jk connector tomcat 4.1.27 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » Tomcat
Bookmark "jk connector tomcat 4.1.27" Watch "jk connector tomcat 4.1.27" New topic
Author

jk connector tomcat 4.1.27

john skolof
Greenhorn

Joined: Oct 13, 2003
Posts: 1
We have a web application running on tomcat 3.2.4 fronted by Iplanet using the AJP 1.3 jk connector. The tomcat instance is running on "machine_1" and the web server on "machine_2". machine_2 has the domain name foo.com and has ssl turned on.
The welcome file for our application is index.jsp. With tomcat 3.2.4 and the jk connector the application is accessible at both https://foo.com/webapp/ and https://foo.com/webapp/index.jsp.
We wanted to switch to a newer version of tomcat. We shutdown the 3.2.4 instance and configured a 4.1.27 instance using the deprecated jk connector so that we wouldn't have to upgrade/change our web server configuration.
Now with tomcat 4.1.27 everything is redirected properly through https://foo.com/webapp/index.jsp.
However when https://foo.com/webapp/ is hit the redirect doesn't work properly. According to the catalina_log file (we turned debug all the way up) when https://foo.com/webapp/index.jsp is hit the AJP13 connector properly gets the referer as https://foo.com/webapp/index.jsp. However when https://foo.com/webapp/ is hit the referer resolves to https://machine_2.com/webapp/ . The application is served up but instead of https://foo.com/webapp/ in the address bar https://machine_2.com/webapp/ is shown.
Since our security certifcate is for foo.com the user is given a warning that the certifacte is invalid if they use the url https://foo.com/webapp/
This error does not occur if they use the URL https://foo.com/webapp/index.jsp
Again with tomcat 3.2.4 and the jk connector to the web server works fine. Upgraded to 4.1.27 tomcat (and kept the web server the same) and the jk connector only partially works.
Any ideas?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: jk connector tomcat 4.1.27