tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <>
Subject Re: Any reason to use Apache w/ Tomcat for webapp with all dynamic web pages?
Date Tue, 02 Oct 2001 03:02:42 GMT

On 1 Oct 2001, David M. Karr wrote:

> Date: 01 Oct 2001 18:20:07 -0700
> From: David M. Karr <>
> Reply-To:
> To:
> Subject: Any reason to use Apache w/ Tomcat for webapp with all dynamic
>     web pages?
> If you're committed to a project where virtually all of the pages will be
> dynamically generated, through JSP most likely, and you're committed to using
> Tomcat, is there ANY good reason to use Apache, in addition to Tomcat?

Good reasons to use Apache (or any other web server) in conjunction with

* If you have Apache already installed, and don't want users to use
  a non-port-80 URL for JSP/servlet based applications.

* If you need other functionality that Apache provides in addition
  to support for servlets and JSPs that Tomcat provides.

* If you are doing *lots* of SSL stuff (current C-based implementations
  of SSL work faster in Apache, but the gap is narrowing).

* If you need to run on port 80 and be non-root (although this is getting
  addressed in current versions of Tomcat).

* If you have lots of static content that can be served from a directory
  other than the webapp's context path  (right now, current Tomcat
  versions serve static content within the webapp directory faster
  stand-alone than they do behind Apache).

When one or more of these reasons is applicable, definitely use Apache in
front of Tomcat.

If one of these reasons doesn't apply, then IMHO you are much better
served just running Tomcat stand alone.  As an extra added bonus, you get
to keep all the hair you'd be pulling out trying to configure
Apache+Tomcat :-).

But, overall, isn't it nice to have a choice?

Craig McClanahan

View raw message