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 andrewcwinter@gmail.com
 designates 74.125.82.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <51240332.30805@ice-sa.com>
References: 
 <CAPX=uDJ9qdK6Ou-xfULzf45dH=60irtD0Q8-Fptt=drVvGJ87g@mail.gmail.com>
	<51240332.30805@ice-sa.com>
Date: Tue, 19 Feb 2013 18:50:41 -0500
Message-ID: 
 <CAPX=uDJDFXVTCNFV5OYN_YxnPNi-vNJE4cn0UNo=d-82buBDHw@mail.gmail.com>
Subject: Re: basic auth required on https but not required on http
From: Andrew Winter <andrewcwinter@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=e89a8f3ba6e365265004d61c824a

--e89a8f3ba6e365265004d61c824a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks. A lot of file IO goes on with this app. There are a couple of files
in particular that are held open for the life of the app and written to
sporadically. I am thinking that having the same code as two web apps would
lead to those files getting clobbered. Is there a way to make the 'same
appbase with 2 hosts' version work?
On Feb 19, 2013 5:57 PM, "Andr=C3=A9 Warnier" <aw@ice-sa.com> wrote:

> Andrew Winter wrote:
>
>> I work on an intranet type application.  While on the local network call=
s
>> are made to regular http and authentication is not allowed due to a larg=
e
>> number of established services that call the server without providing
>> authentication.  However, the server accepts calls from the outside over
>> SSL (regular http port is blocked by firewall). In these cases the use o=
f
>> basic authentication is required.  I don't see a way to have work like
>> this.  With our older setup we used Apache as a front end and had a
>> virtual
>> host file for each port.  One used https and basic auth and the other
>> didn't. Both pointed to the same web app.  Now I must send calls directl=
y
>> to Tomcat as we are implementing asynchronous requests.  What can I do
>> here?
>>
>>
> Do the same as under httpd (except one thing) : use separate <Host>'s
> within the Tomcat configuration (same as <VirtualHost> under Apache).
> Deploy a separate copy of your webapps within each <Host>'s "appBase". In
> one <Host>, you protect them via Basic Auth, in the other <Host> you do n=
ot.
>
> Under Tomcat, it is not recommended to use the same "appBase" (roughly th=
e
> same
> as Apache's "DocumentRoot") for two separate <Host>'s, because this
> creates problems of double deployment etc.  So use two separate sets of
> webapps.  They are still the same webapp, just deployed twice, in differe=
nt
> locations.  Is that a problem for you ?
>
> Roughly (check the proper syntax on tomcat.apache.org) :
>
> server.xml :
>
> ....
>
>   <Engine ...>
>
>     <Host name=3D"host1.company.com" appBase=3D"/some/dir/number1" ..>
>        ...
>     </Host>
>
>     <Host name=3D"host2.company.com" appBase=3D"/some/dir/number2" ..>
>        ...
>     </Host>
>
> ...
>
> /some/dir/number1
>     |- ROOT/
>     |- webapp1
>     |- webapp2
>
> /some/dir/number2
>     |- ROOT/
>     |- webapp1
>     |- webapp2
>
> the 2 "webapp1" are the same (same code, same files,..) (*)
> the 2 "webapp2" are the same
>
> (*) actually, almost the same, since their WEB-INF/web.xml will be
> different : one has to be accessed via HTTPS and use Basic Auth, the othe=
r
> one not.
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.**apache.org<users-unsub=
scribe@tomcat.apache.org>
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

--e89a8f3ba6e365265004d61c824a--