On Oct 16, 11:36 pm, "Marc Gravell" <marc.grav...@xxxxxx> wrote:
> On my F5 setup, I believe the network team configured it so that the
> F5 deals with the public SSL and compression, and then there is a
> second SSL session between the F5 and the web-farm.
It turns out that this would be difficult to do in my case. The IIS
that the WCF service is running on hosts a number of services all
hosted in a single IIS instance. These services have different
external DNS names and IIS only allows one certificate to be installed
per instance of IIS -- it turns out that the certificate that is
already installed in the IIS instance does not correspond to the DNS
name that my service is associated with. So I can't actually get an
HTTPS connection from the front end device to the internal server.