tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Bailey" <>
Subject RE: AJP Connector - Problems Proxying HTTPS Connections
Date Mon, 05 Feb 2007 20:49:32 GMT
Thanks, Charles.

The main reason for deploying behind httpd rather than standalone was to
leave a bit more flexibility in the event we decide to deploy one or
more other non-J2EE (e.g. PHP) web applications to this same server at a
later date, should that become desirable or necessary. I've also heard
that the httpd SSL implementation is faster than Tomcat, but perhaps
that is now a thing of the past.

Thanks for setting me straight on the ROOT context. I got the same
comment from someone else. This will probably be the next thing I try
since I have this working in a similar configuration for another

At this point, any approach that works is a good one, but even though I
may not have needed to take the approach I selected, I'm still curious
to know what I did wrong. So if anyone sees the reason why this approach
could never have worked or sees an error in my configuration, I'd still
be interested.

Thanks again.

Bill Bailey

-----Original Message-----
From: Caldarale, Charles R [] 
Sent: Monday, February 05, 2007 3:25 PM
To: Tomcat Users List
Subject: RE: AJP Connector - Problems Proxying HTTPS Connections

> From: Bill Bailey [] 
> Subject: RE: AJP Connector - Problems Proxying HTTPS Connections
> I have a J2EE (Struts) Application running in Tomcat. I want
> to use Apache HTTPD to provide the HTTPS connections and simply
> proxy all requests to the Tomcat container.

It seems like you're going through a lot of unnecessary work & headaches
to put httpd in front of Tomcat; if you don't have some other pressing
need, why not just run Tomcat standalone?  It handles SSL quite nicely.

> Another constraint is that I want the web site to
> be accessible by just its hostname and domain (e.g.
> and I don't want to
> require a servlet context path to be typed as part
> of the URL every time one accesses the site.

Then simply deploy your application as ROOT.

> 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.

You laboring under a misconception - the only ROOT application in Tomcat
is its default welcome page; manager, admin, the examples, etc., are all
deployed as independent applications and are still available even if
ROOT has been replaced.

> Therefore, I decided to have a second virtual host on
> the Tomcat side.

You're going through a lot (a whole lot) more work than you need to.

 - Chuck

MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message