Re: mod_webapp connector on linux

2001-10-03 Thread Matias Bahlenberg
I recognize this problem, and it seems like a connector-problem. The Apache Server can not connect to Tomcat. I solved it with starting Tomcat before starting Apache. This means that everytime I have to restart Tomcat, I have to restart Apache. // Matias - Original Message - From: "Ja

Re: HTTP Status 500 - Now Exception

2001-09-27 Thread Matias Bahlenberg
> I use request.getAttribute("javax.servlet.request.X509Certificate") to > extract the certificate string. > > Any ideas anyone. > > > java.lang.ClassCastException: [Ljava.security.cert.X509Certificate; > at .. > > > > &

Re: HTTP Status 500

2001-09-26 Thread Matias Bahlenberg
Hi Lee, I recognize this. I solved the problem with a Host inside the Engine element in the server.xml. See below:

Re: Tomcat 4.0 & Apache with Client Certs

2001-09-25 Thread Matias Bahlenberg
Hi, I have tried to get the client certificate information too, but with no success. I use Apache 1.3.19 with Tomcat 4.0. I have been told that when using a connector with Apache & mod_ssl it is essential to specify "SSLOptions +StdEnvVars +ExportCertData. Otherwise mod_ssl will not produce t

SSL environment variables in Tomcat 4.0?

2001-09-21 Thread Matias Bahlenberg
Hi, How do I obtain information of the Apache additional environment variables: "SSL_CLIENT_CERT" and "SSL_SERVER_CERT" in Tomcat 4.0? I am using Tomcat 4.0 (final release) as servlet-container, connected via mod_webapp (WarpConnector) to Apache Web Server 1.3.19. The Apache Server is config