I’ve got a situation where I have a WCF load balancer sitting behind a F5 load balancer that is doing the SSL decryption and forwarding the unencrypted message to the BizTalk hosted WCF service behind it.
If I configure the service using basic http and the client attempts to call the service this comes back:
The provided URI scheme 'https' is invalid; expected 'http'. Parameter name: via
If I configure the service to use wcf-custom and set the bindings for wsHttp with windows auth or None the client gets the following exception:
There was no endpoint listening at https:/// service.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
I think that the answer to this may involve using a custom behavior, however I was wondering if anyone had run into this situation in the past, and if so, how did you deal with it?