I am trying to make a back-end mod_perl/mod_ssl server. The front-end
server that is currently in place is doing a great job forwarding normal
requests to the back-end, but it is not forwarding SSL. Now, the front-end
server does not understand SSL, itself. What I'm doing is trying to force
The front end server must be configured to understand SSL. Otherwise, how
else can the HTTP request be pulled apart (decrypted) to understand that it
has to be forwarded to the backend server.
If you configure the back-end server to understand SSL, that's OK, but
beware that all mod_proxy is
At 07:05 PM 7/25/2001 +0200, Issac Goldstand wrote:
The front end server must be configured to understand SSL. Otherwise, how
else can the HTTP request be pulled apart (decrypted) to understand that
it
has to be forwarded to the backend server.
2 words: dumb proxy. The request doesn't
The front end server must be configured to understand SSL. Otherwise,
how
else can the HTTP request be pulled apart (decrypted) to understand
that
it
has to be forwarded to the backend server.
2 words: dumb proxy. The request doesn't need to be pulled apart by the
front-end server
At 01:19 AM 7/26/2001 +0200, Issac Goldstand wrote:
[snipped]
I see what you mean. I'm not dealing with client certs (yet), and I'm
thinking that when the system that I'm testing now goes production, it'll be
a front-end SSL, back-end non-SSL sorta deal... But that won't work for now
due to
