On Mon, 24 Jun 2002, Philip Ravenscroft wrote:
> > The reverse proxy should now make an SSL connection to
> > webserver (this is
> > running IBM HTTPServer, IBM's packaged Apache). webserver has it's own
> > self-signed certificate.
>
> Out of the box, mod_proxy cannot negotiate secure connections, so it can't
> connect to your backend server using https. (I don't know if anyone has
> gotten this to work, though). This means that you should have the backend
> proxy connect in the clear to your IBM server.
Normally, one uses mod_rwrite on the exposed server to communicate with an
internal reverse proxy or the actual content server. The content returned
by the internal server can be returned using mod_proxy.
Ralph Engelshall wrote a paper on mod_rewrite in the late Nineties that
has a lot of detail on the function and use of this module. Reading the
paper is time well spent.
Nothing up this sleave. ... Ooh! I don't know my own strength!
Bullwinkle J Moose
Merton Campbell Crockett
--
BEGIN: vcard
VERSION: 3.0
FN: Merton Campbell Crockett
ORG: General Dynamics Advanced Information Systems;
Intelligence Solutions
N: Crockett;Merton;Campbell
EMAIL;TYPE=internet: [EMAIL PROTECTED]
TEL;TYPE=work,voice,msg,pref: +1(805)497-5045
TEL;TYPE=pager,msg: +1(877)528-0049
TEL;TYPE=fax,work: +1(805)497-5050
TEL;TYPE=cell,voice,msg: +1(805)377-6762
END: vcard
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
