Hassan, Thanks for your help. I am going to try making my app the ROOT context for the default host and get rid of the virtual hosts on the Tomcat side. If that still doesn't work, I'll try some of your troubleshooting ideas.
I actually tried using mod_proxy_http once in my many attempts to find a solution and had problems there, too, but I've been through so many iterations now, I won't swear to exactly what I did or didn't try. You are right. This really shouldn't be this hard. And I didn't expect it to be when I started (after all, I did this for another application in far less time), but once I committed to an approach I was like an old dog with a bone and refused to let it go until I got it working. Maybe a new direction will be the ticket to getting me past this. Thanks again. Bill Bailey -----Original Message----- From: Hassan Schroeder [mailto:[EMAIL PROTECTED] Sent: Monday, February 05, 2007 3:33 PM To: Tomcat Users List Subject: Re: AJP Connector - Problems Proxying HTTPS Connections On 2/5/07, Bill Bailey <[EMAIL PROTECTED]> wrote: > So the context (which I don't want visible to the end users) has > 'escaped' into the browser world. I found that this was not a problem if > I made my application appear in the ROOT context for the server, but > didn't want to remove the standard ROOT applications (manager, etc.) for > the local host. Therefore, I decided to have a second virtual host on > the Tomcat side. whoa, you lost me here. The manager is a separate Context -- there's no reason you can't have your app as the ROOT context on the default host. Still, > One of my next tests is going to be to replace this > JSP with a vanilla HTML file to eliminate for certain the possibility > that my application is doing this unwanted redirect, but I'm reasonably > confident that it isn't. Not a perfect test, since your app might have some Filter doing stuff that's non-obvious :-) Anyway, here's my suggestion: replace your current app with a very skeletal web app, just an index.html, say, so you know there's nothing wierd going on. Try that. If that still doesn't work, change your httpd proxy to use mod_proxy_http and forward to your 8080 port. At the worst, you can sniff that traffic to see what's really happening :-) This really shouldn't be this hard -- I've set up a similar config (but with multiple virtual hosts) pretty recently, and there was nothing to it. HTH, -- Hassan Schroeder ------------------------ [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
