Unfortunately, it seems that the answer
is.....................................
#1.
Nobody seems to have successfully reverse proxied to a https server on a private
(192.168) network
https-------->Straight thru proxy---------->https cert
authentication + (perl $ENV{'SSL_CLIENT_S_DN_CN'} stuff.)
I will
look at implementing the following less secure method.
https-------->Authenticating Proxy + (perl $ENV{'SSL_CLIENT_S_DN_CN'}
stuff.)---------->Plain old http +
NFS.
OR
VPN
Cheers,
Roy
Preece
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Roy Preece
Sent: Wednesday, July 11, 2001 9:22 PM
To: [EMAIL PROTECTED]
Subject: Reverse Proxy SSLOK, from the lack of response to my previous email (SSLClient Browser <--> Apache Proxypassreverse <--> https://192.168.xxx.xxx) I can deduce one of two cases is true.1. Nobody has successfully achieved a reverse proxy of SSL in the way I am describing, (Hard to believe)or...........2. You are really sick of this question.(Sorry)If you chose 2, I have read through all of the mail archives on this list and others with regard to reverse proxying https. The most popular config seems to be to run SSL between the browser and the proxy server and then plain old http between the proxy server and the backend private servers. However, I want the client browser to use a cert to authenticate directly on the back end server on a private network, therefore I just want the reverse proxy to pass the encrypted traffic back and forth.Is this possible..................How? Tips and pointers greatly appreciated.TIA,Roy Preece
