| anthony.carrigan@ntlworld.com 2004-01-19, 3:02 pm |
| You need to have the certificate on the reverse proxy for the client to make a secure connection across the internet.
For maximum security, you can also have the same certificate on the back-end server and use 'SSL bridging' i.e. use a PROXY statement in WTE to
make a second-stage SSL connection from the reverse proxy to the back-end server.
There are a couple of flaws in the documentation concerning SSL and PROXY directives - see
the reply I gave to the "Setting up multiple SSL certs using WTE version2.0" posted by "cjay" on 24/02/03
Tony Carrigan (Abbey National Glasgow)
tony.carrigan@anfis.co.uk
On Mon, 26 Aug 2002 08:53:02 -0400, "stewart" <stewartnospam@rogers.com> wrote:quote:
> Hi,
>
> I am running a single node (standalone server) using IBM HTTP server,
> WebSphere App Server v3.5 and DB2 v7.1. Various pages use SSL. I want to
> put Edge server v1 (Web Traffic Express v3.6?) on a machine to act as
> reverse proxy.
>
> It installs/runs out of box fine and works great with standard http.
> However, any pages using SSL make the client's (user's) browser go to the
> backend server (it shows up in the url bar, rather than the reverse proxy
> machine).
>
> As I am not using load balancing (only one node) ... is it possible to make
> the reverse proxy work with the SSL certificate still on the WebSphere App
> box, or is it manditory to move the certifiicate to the reverse proxy box?
>
> Thanks in advance!
>
>
>
|