Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Overview > Deployment options
*
As an explicit proxy in which the user's browser or client software is configured to send requests directly to Content Gateway. See Explicit Proxy.
*
As a transparent proxy in which user requests are transparently routed to Content Gateway on their way to the destination server. The user's client software (typically a browser) is unaware that it is communicating with a proxy. See Transparent Proxy and ARM.
Important 
Even when SSL Manager is not enabled and HTTPS is not decrypted, Content Gateway performs HTTPS URL filtering. This means that for every HTTPS request, a URL lookup is performed and policy is applied.

Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Overview > Deployment options