HTTP profile & SSL profiles not playing nice.
So I am attempting to set up a VS that is HTTPS (443) listening and HTTPS (443) pool members. I use a standard VS. Here is where it gets interesting. If I DO NOT use an HTTP profile the HTTPS/SSL connection get proxied to the pool server just fine. If I add an HTTP profile and a certificate based Client SSL profile with standard Server SSL profile the connection does not work. However, if I changes the Client & Server SSL profiles to Proxy the SSL it works again.
I appears that having the F5 be the "man in the middle" is not being accepted by the back end pool member. I am not sure why this would be the case, but I have run myself into the ground messing with profiles and having the server admins changing setting on the servers. I am at a loss as to why this would happen.
Does anyone have any insight?
What more info do you need? (I am limited as to what I will be able to provide)