> If you won't re-name the web application, I think redirects will be > your best bet. If a client requests http(s)://share2.domain.tld/, you > should redirect them to https://share2.domain.tld/share/ and then > "JkMount /share/* worker1". You can redirect using RedirectPermanant > or a few other things like having an index.html with an HTTP-EQUIV > header in it. > > At this point, you seem to be able to successfully connect httpd -> > Tomcat. If you don't want to follow our advice for a more robust > configuration, you don't have
You know what Chris, I am trying to follow your advice! Forgive me if I am not a tomcat expert like you and others on this list! I keep inviting you or anybody else that would, to either contact me off list for all the full links/info or maybe a remote session. I know I have a working config on a server that I am trying to upgrade using, what looks like , Apache mod_rewrite and mod_jk but this is expensive and I heard mod_jk is much better. The offer still stands for either a off list contact or teamviewer session (I am willing to pay). --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
