At present we do not need to perform discretionary access controls.
Still I am very interested in the way you approached the problem.
Could you please give me some more infos on how you managed to configure
the reverse proxy in order for it to speak https with the web server?
What is really confusing me (I am quite a newbie) is the way how the two
web servers can initiate the ssl handshacking......
I do believe that you used something different than Apache + ModSSL.......
Thank you very much for your answer :-)
Best regards,
Costantino Imbrauglio
IT Staff - BancaIMI S.p.A.
[EMAIL PROTECTED]
Merton Campbell Crockett <[EMAIL PROTECTED]> on 28/02/2000 16.11.39
To: Costantino Imbrauglio/MI/IMISIGECOSIM
cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
Alessandro Pengue/MI/IMISIGECOSIM, Luca
Castiglioni/IMISIGECOSIM, Giovanni
Boniardi/IMISIGECOSIM, Leonardo
Rosa/IMISIGECOSIM, Alessandro
Zappa/MI/IMISIGECOSIM, Simone
Bonali/MI/IMISIGECOSIM
Subject Re: Accel. Proxy Config with Apache 1.3.12 +
: ModSSL 2.6.0
On Mon, 28 Feb 2000 [EMAIL PROTECTED] wrote:
> 1) User browser speaks https with the reverse proxy; reverse proxy speaks
> http with the web server
If your actual web server uses discretionary access controls, this is the
approach that you must take. Using Server/Server certificates needed for
your second approach resulted in a loss of user identity when we started
doing this several years ago.
> 2) User browser speaks https with the reverse proxy; reverse proxy speaks
> https with the web server
Merton Campbell Crockett
Costantino Imbrauglio
Information Technology -
Banca IMI - Milan
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
