Dropped HTTPS connections
Some application protocols that tunnel using port 443 may attempt to establish a connection with Content Gateway using a variant of HTTPS that Content Gateway doesn’t accept. When HTTPS is enabled in Content Gateway, these attempted connections are dropped by Content Gateway. Connections using QIP 2005 are an example of this type of application protocol.
When HTTPS is disabled, SSL connections don’t pass through Content Gateway and this type of connection is not an issue.
When HTTPS is enabled, the issue can be handled in either of two ways:
- Configure Content Gateway to tunnel unknown protocols.
- Add incidents to the Content Gateway SSL Incidents list to tunnel these application protocols.