This came up yesterday. According to one poster, putting
DirectoryIndex index.jsp
in your httpd.conf VirtualHost block would cause Apache to translate
"http://192.168.168.45/rtizon"; into "http://192.168.168.45/rtizon/index.jsp";.
However, it doesn't work at all for me, never has, and I have always understood it to be a limitation of using mod_jk (and possibly mod_jk2).
What happens when you try "http://192.168.168.45/rtizon/";?
John
Ray Madigan wrote:
I have mod_jk working with two workers and a loadbalancer.
when i use http://192.168.168.45:8080/rtizon the browser completes the line with /index.jsp.
Same is true with the other worker and the correct page comes up
when i use http://192.168.168.45/rtizon i get a page not found error?
and when I complete the url with http://192.168.168.45/rtizon/index.jsp i get the correct page
My JkMount entries are
JkMount /*.jsp loadbalancer JkMount /rtizon loadbalancer JkMount /rtizon/*.jsp loadbalancer
Is this the expected behaviour or should apache complete the url as tomcat does cause it is making the call to tomcat?
And, do I need the second JkMount /rtizon loadbalancer?
Thanks
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
