Return-Path: <rslifka@home.com>
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 14444 invoked from network); 12 Jul 2000 14:55:40 -0000
Received: from ha1.rdc2.bc.wave.home.com (HELO mail.rdc2.bc.home.com)
 (24.2.10.68)
  by locus.apache.org with SMTP; 12 Jul 2000 14:55:40 -0000
Received: from cr699264a ([24.113.17.57]) by mail2.rdc2.bc.home.com
          (InterMail vM.4.01.03.00 201-229-121) with SMTP
          id <20000712141348.ZGTK9731.mail2.rdc2.bc.home.com@cr699264a>;
          Wed, 12 Jul 2000 07:13:48 -0700
From: "Rob S." <rslifka@home.com>
To: <tomcat-user@jakarta.apache.org>,
	"Brian Richards" <ncmusic@pobox.com>
Subject: RE: configuring a single port
Date: Wed, 12 Jul 2000 07:15:58 -0700
Message-ID: <000c01bfec0b$b33a48c0$39117118@rct1.bc.wave.home.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_000D_01BFEBD1.06DB70C0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <007101bfec00$0200df70$32cc2509@raleigh.ibm.com>
Importance: Normal

This is a multi-part message in MIME format.

------=_NextPart_000_000D_01BFEBD1.06DB70C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hi Brian,

> So I would have to comment out
> <!-- Normal HTTP -->
>         <Connector className="org.apache.tomcat.service.PoolTcpConnector">
>             <Parameter name="handler"
>
> value="org.apache.tomcat.service.http.HttpConnectionHandler"/>
>             <Parameter name="port"
>                 value="8080"/>
>         </Connector>

Tomcat is a web server as well as a JSP/Servlet container.  You're
commenting out the web server portion when you do that.  There are no other
implications of commenting out this line other than removing Tomcat's
ability to respond to HTTP requests.

> If  want apache to handle all Http request and only tell tomcat to handle
> the
> servlet and jsp stuff?

A few days ago, there was a small thread on this.  I'll attach a message
Craig wrote, all of which I keep in a special folder for Tomcat reference
info =p

- r

------=_NextPart_000_000D_01BFEBD1.06DB70C0
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment

Reply-To: <tomcat-user@jakarta.apache.org>
From: "Craig R. McClanahan" <Craig.McClanahan@eng.sun.com>
To: <tomcat-user@jakarta.apache.org>
References: <000501bfea48$a01f1640$39117118@rct1.bc.wave.home.com>
Subject: Re: Apache & Tomcat cooperation
Date: Mon, 10 Jul 2000 08:56:43 -0700
Message-ID: <3969F23B.2ACAB0A5@eng.sun.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Mozilla 4.72 [en]C-CCK-MCD {Sony}  (Win98; U)
X-No-Archive: yes
list-help: <mailto:tomcat-user-help@jakarta.apache.org>
list-unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
X-Accept-Language: en

"Rob S." wrote:

> > Now I guess I'd still have to have a look at the server.xml file
> > at least if I want to specify to TomCat that I want Apache to
> > process the static HTML files & images, wouldn't I?
>
> That's one thing I've never been quite sure about, but I really should be
=)
>
> For example, let's say you mount your default context to the root of a
> virtual host.  Will all requests to that host be sent to Tomcat, even ones
> that are for HTML and images?  If so, it would seem as though mounting a
> context under a certain path and wanting Apache to serve static files
under
> that same path while mounted would be mutually exclusive goals.
>
> Anyone mind shedding some light on this?
>

The "$TOMCAT_HOME/conf/tomcat-apache.conf" file that is generated
automatically
every time you start Tomcat attempts to set things up so that static files
are
served by Apache, while JSP pages and servets are executed by Tomcat.  It
does
so by generating a series of Apache configuration directives for each
context
that you've defined in your server.xml file (plus those that are
automatically
recognized in the webapps directly in Tomcat 3.2).  For the /examples
context,
the generated commands look like this:

    Alias /examples "/path/to/tomcat/webapps/examples"
    <Directory "/path/to/tomcat/webapps/examples">
        Options Indexes FollowSymLinks
    </Directory>
    ApJServMount /examples/servlet /examples
    <Location "/examples/WEB-INF/">
        AllowOverride None
        deny from all
    </Location>

In English, these commands roughly do the following:

* Whenever Apache sees a request that starts with
  "/examples", go to the specified directory on your
  disk.  This causes static files to be served from here
  by Apache unless overridden elsewhere (see below).

* When serving static files, apply the usual Indexes
  and FollowSymLinks options

* Any request that starts with "/examples/servlet" should
  be passed on to Tomcat's "/examples" context for
  execution (i.e. run a servlet).

* Do not serve any static files from "/examples/WEB-INF"
  (this follows the servlet spec rule that you are not allowed
  to serve these files directly to a client.)

There is an additional rule at the top of the file that causes all JSP pages
to
be executed by Tomcat:

    AddHandler jserv-servlet .jsp

The mechanism in the generated file is not perfect (for example, it doesn't
know
about any <servlet-mapping> entries you have defined in your "web.xml"
file),
but it gives you a starting point for integrating Tomcat with Apache.  For
more
information, see the "Minimalistic User's Guide" document included with
Tomcat,
and the standard Apache configuration documentation.

>
> - Rob

Craig McClanahan


------=_NextPart_000_000D_01BFEBD1.06DB70C0--