Forum Discussion
NimbostratusIIS 8 SSL F5 configuration
Several IIS 8 Webservers with valid certificates and windows authentication enabled are placed behind F5 with balancing based on ssl session id. But there is persistent strange behaviour with "server not responding" "socket closed" and "access denied" errors, while with single web server all works perfect, where can be a problem?
- Kevin_Stewart
Employee
There are probably two issues here.
-
As a general rule, SSL session ID persistence is ineffective for browser-based communications. Modern applications frequently renegotiate TLS sessions, which changes the session ID. For HTTP traffic, the very best persistence method is usually cookies.
-
When you say "windows authentication", are you talking about client certificate authentication? And are you not terminating the SSL between the client and the web servers?
-
