Redirection to pools failing

Thanks, Richard, I understand. I just did not realize that destination uri is also encrypted in coming packets. Probably makes sense since that's all data sent by the browser. Though then - when server with multiple sites accepts the call it needs to direct it to appropriate site, so it would need to decrypt data first, for which it needs to know which certificate should be used, for which it needs to know the name of the site the call is directed to, which in turn is in the encrypted data. I wonder how does it do then. I guess if all certs have the same secret key then its ok. Or if the initial request has plain text destination uri before encrypted tunnel is created between server and browser. Simple (though not necessarily true) logic says its the latter - call first needs to get to destination somehow, return authenticated identity back to the browser and then exchange keys and start encrypting/decrypting. If correct, then it gives F5 opportunity to start redirect without further reading encrypted data.

I'll check on the link you provided and try to implement. I got the idea, just need to think how to redirect at the same time http and/or https to separate pools and http calls to https. Its easy to send from http to https and I think I understand whats needed to redirect to appropriate pool based on uri, but how to combine them together still eludes me. Need to try. But I don't intend to direct from one member to another in the same pool, I guess I confused you with my description. And, actually in my case, incidentally both certificates are wild cards. But since they are for different domains I don't see how that would help in my case. If by any chance you have some info/link on how to use TLS hostnames you mentioned that would be great.