-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Thomas wrote:
> Paul Puschmann wrote:
>
>> we'd like to use our Tomcat with ssl and client certificates.
>>
>> Does anybody know if the user information (of the user-certificate) can
>> be used to authenticate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
we'd like to use our Tomcat with ssl and client certificates.
Does anybody know if the user information (of the user-certificate) can
be used to authenticate?
Tomcat is 5.5.7
Paul
- --
Linux-User #271918 with the Linux Counter, http://counter.l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Quinton Delpeche wrote:
> When I install Tomcat 5 (base, examples, and admin) I get an error with the
> packages. I read that this is to do with incorrect directory names or link
> names.
>
> On one of my other test machines I keep getting a socket
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
we'd like use use ssl client certificates (stored on smartcards) to
secure the access to one of our servers.
Right now I use an Apache2 with mod_jk, so my apache2 is the ssl
endpoint. That's not so bad, but I am searching for a way to integrate
th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> yes i did exported those env variables.
> but still i am getting the following error
>
> Cannot find ./catalina.sh
> This file is needed to run this program
>
> I have even checked for the file permission mode.
> and also
Tony Stocker wrote:
> All,
>
> I believe that I found my problem, and for the sake of posterity I'm
> posting it for the next poor fool who is forced to chase around the
> web and through books looking for decent documentation.
>
> When I set up Tomcat I copied the sample workers.properties file
Sébastien GALLET wrote:
> Paul Puschmann a écrit :
>
>> Dale, Matt wrote:
>>
>>
>>> 1.2.6 is the latest and should work with Apache 2 so you don't have
>>> to go back to apache 1.
>>>
>>> Ta
>>> Matt
>>>
>&
Dale, Matt wrote:
> 1.2.6 is the latest and should work with Apache 2 so you don't have to go
> back to apache 1.
>
> Ta
> Matt
Okay, but I don't get jk1 for apache2 as a ready debian-package.
I prefer ready-built packages, because otherwise I could miss some
important compiling options or get so
Mladen Turk wrote:
> Paul Puschmann wrote:
>
>> Hi,
>>
>> we want to use Apache2 (2.0.53) as a frontend for out Tomcat (4.1.31)
>> and don't get the right configuration for our jk2 (2.0.4).
>> This all runs with Java 1.4.2_06 on Debian Sarge x86.
>
Hi,
we want to use Apache2 (2.0.53) as a frontend for out Tomcat (4.1.31)
and don't get the right configuration for our jk2 (2.0.4).
This all runs with Java 1.4.2_06 on Debian Sarge x86.
We want to serve two or three different applications through our
apache2. Each one gets its own VirtualHost an
10 matches
Mail list logo