Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of group.vas@gmail.com designates
 209.85.223.199 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=AxBCiZhezxXJO7E4qh/I2aCgqdfqFsg27ns6HwhbcMEnAli4ZSRJ/FGR4NKBBeXoau
         ZCVCwUPvHSzVuIXsfIzhK8CvN2yFgUZd8LQsntfocxZpwPUGPiGJ0vBnNe3lOj+XIqnZ
         k+qAK69pR/6QhxIOr12UkMwC8V+779B5J5IHI=
MIME-Version: 1.0
In-Reply-To: <4B1641DB.6080506@ice-sa.com>
References: <b65609ea0912010639s19af33ddxa1bac72b915c423c@mail.gmail.com>
	 <4B15358C.3050305@ice-sa.com>
	 <4B15CD1B.2020609@christopherschultz.net>
	 <4B1641DB.6080506@ice-sa.com>
Date: Wed, 2 Dec 2009 08:06:15 -0800
Message-ID: <b65609ea0912020806n2c4ef0e3r654b9839203927a8@mail.gmail.com>
Subject: Re: Debugging tomcat<->apache(mod_jk) bridge
From: groupalias v <group.vas@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

In response to Chris' question -   I have only one tomcat instance
running and it picks up the webapps in /srv/tomcat6/webapps/
and the URL www.example.com:8080/test/index.jsp works fine.  I tried
with the mod_jk.c and jk_module with the same result.

In response to Andr=E9's question this is the first time I am hearing
about the SetHandler construct.  Is there documentation somewhere I
can read?
The issue about security is something I am concerned too and thought
its too error prone.

What is the workers.tomcat_home directive in workers.properties used for?

If the communication is over the 8009 port why does apache care about
one of tomcat's directories?

I will re-create the with mo_jk.c and post them.

Thanks,
- Vas

On Wed, Dec 2, 2009 at 2:30 AM, Andr=E9 Warnier <aw@ice-sa.com> wrote:
> Christopher Schultz wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> All,
>>
>> On 12/1/2009 10:26 AM, Andr=E9 Warnier wrote:
>>>
>>> groupalias v wrote:
>>>>
>>>> httpd.conf
>>>> -------------
>>>>
>>>> LoadModule jk_module =A0 =A0 =A0 =A0 =A0modules/mod_jk.so
>>>>
>>>> <IfModule jk_module>
>>>
>>> What the h.. is this line for : ?
>>
>> It's for conditional inclusion of Apache httpd directives when modules
>> may or may not be loaded.
>
> No. I was talking about the "Alias" which follows. Hence the trailing ":"=
 in
> my question. Ok, following the colon by a question mark wasn't the cleare=
st
> thing either...
>
>
> =A0The test I have in my httpd.conf is:
>>
>> <IfModule mod_jk.c>
>>
>> I can't find any references online to the use of jk_module in
>> <IfModule>, so the OP might want to change it.
>>
>>>> Alias /test/ "/srv/tomcat6/webapps/A"
>>>
>>> It kind of contradicts these next lines :
>>>
>>>> JKMount =A0 =A0 =A0 =A0/test/ A
>>>> JkMount =A0 =A0 /test/* A
>>>
>>> Because of the Alias line, I don't think that mod_jk even gets to see
>>> your /test/ URLs.
>>
>> No, mod_jk gets higher priority than mod_alias. I'm not entirely sure
>> how the pecking order is decided, but I do know that mod_jk gets first
>> shot.
>
> Yes, +1 about the "not sure". That is why I prefer, rather than JkMount, =
the
> form with
> <Location /test>
> =A0SetHandler jakarta-servlet
> =A0...
> </Location>
>
> At least in that case the precedences are clear, and I find that this syn=
tax
> fits better with "the Apache way of things", and is much more flexible th=
an
> JkMount/JkUnMount.
>
> My general gripe about that Alias line, is that it generally gives access
> for Apache, to the entire tomcat webapps directory, thus from the start
> bypassing anything configured at Tomcat level in terms of security. =A0Th=
en
> later, one has to "patch" this hole by a series of conditional Deny rules=
,
> hoping not to forget one.
> And in 99% of the cases, one does forget something, such as also forbiddi=
ng
> META-INF e.g.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org