I assume that you mean the client-cert. Firstly, I don't think that you can get this passed from mod_proxy to Tomcat (but I could be wrong, I've never tried :). It looks like the client doesn't have any valid certs to send (the blank dialog). You could try setting 'SSLVerifyClient optional' to verify this (but it's a potential security hole in production).
I'm using Apache 1.3.x, but I've never had a problem with mod_proxy and https -> http connections. "Jennifer Shi" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Hi, We have an web application running on Tomcat. However we can not get SSL certificate on Tomcat. So we installed Apache+SSL which will proxy the HTTPS request to HTTP requests to Tomcat using mod_proxy. Apache_nonSSL+mod_proxy+Tomcat_nonSSL works well. However Apache_SSL+mod_proxy+Tomcat_nonSSL does not work. Specifically, a blank diaglog box is popped up when user clicked on the login button of a page. Meanwhile Tomcat ouputs the following logs. ----- 2003-08-06 08:54:47 - Ctx( ): 400 R( /) null 2003-08-06 08:54:47 - Ctx( ): IOException in: R( /) Socket closed ----- We have configured Apache to proxy the httpS requests to HTTP requests to Tomcat. Somehow Tomcat still receives SSL requests. Does anyone know where we could find the documentation on Apache_SSL+mod_proxy+Tomcat_nonSSL? I have read some documentation on mod_jk but our customer uses mod_proxy. Any clue is appreciated. Apache is 2.0. Tomcat is 3.2.5. Thanks, Jennifer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
