Hi, Perhaps a little off-topic, but think it is still relevant. Now our ca is nearing completion we are thinking about setting up a pilot testsite. What we want to do is the following: Outside <--> WebsiteA <-- |firewall| --> WebsiteB We want our employees to be able to get to websiteB through our firewall only through websiteA. All webcommunication should be https. WebsiteB (or more, the host serving websiteB) only accepts connections on port 443 from the host that's serving websiteA. For http this is easily done, just compile mod_proxy in apache, set the ProxyPass directive correctly and everything for websiteB goes through A. But with https a problem occurs, the communication is not entirely finished. It seems (after viewing what happens when connecting directly to websiteB) the pieces that are not correctly displayed are those pieces that are only displayed after websiteB has offered (and the normal browser has accepted) its server certificate. The way I figure websiteA somehow has to be made aware there is a certificate presented, or I am using the mod_proxy totally wrong (in which case I apologize for posting this message here). Can anyone shed some light on this? Jan -- alive ~ true ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
