Forum Discussion
why do connections stop working when http profile is added to virtual server
The port 443 virtual would have failed if all it had was an HTTP profile but no client SSL profile. The BIG-IP system can't process the HTTP payload at layer 7 (which is what the HTTP profile tells it to do) if the payload is encrypted - hence the need for a client SSL profile to decrypt it first.
The port 80 virtual server should not fail with an HTTP profile, unless the traffic was not HTTP. Having an HTTP profile on this virtual does not matter except from a performance perspective. In other words, if you do not need to process the HTTP payload at L7 (as would be the case if you had an associated iRule that sent an HTTP response), then the HTTP profile is unnecessary. But it should not prevent the virtual server from working.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com