If a Virtual Service is created on port 443, the LoadMaster assumes the service will be supporting HTTPS. These settings make certain features configurable, such as SSL Acceleration. If enabled, the service will allow the configuration of a more verbose HTTP-feature set which includes caching, compression, intrusion detection and content filtering. When utilizing SSL acceleration, the connection between the client and LoadMaster will be secure. The LoadMaster can then contact your Real Server pool using HTTP or HTTPS. The servers may require a specific protocol to be used - that's where the LoadMaster can help.
When SSL Acceleration is enabled and re-encryption is not, the LoadMaster will contact the server via HTTP. The configuration of the health checks is important. Scroll to the bottom of the Virtual Service configuration page and expand the Real Servers section.
HTTP Protocol should be selected. Also, note that the Port listed when you add a new Real Server is 80. This was automatically adjusted by the LoadMaster, from its previous configuration of HTTPS and port 443.
If SSL Reencrypt is enabled as well, the port and health check will change to HTTPS and 443. This is due to the fact that when SSL reencryption is enabled, a HTTPS connection to the servers is utilized.