Restarts the proxy and manager services (the content_gateway and content_manager processes). You must restart the proxy and manager services after modifying certain configuration options. A message is displayed in the manager when a restart is required.

IMPORTANT: In a cluster configuration, the Restart button restarts the proxy and manager services on all nodes in the cluster.

Enables/disables Content Gateway HTTPS traffic management and security analysis. After selecting HTTPS On, you must provide additional information about the Configure > Protocols > HTTPS page and on the Configure > SSL pages. See Working With Encrypted Data.

Enable this option to use a WCCP v2-enabled router for transparent redirection to Content Gateway. WCCP v1 is not supported.

See Transparent interception with WCCP v2 devices.

When this option is enabled, Content Gateway resolves DNS requests on behalf of clients. This option offloads remote DNS servers and reduces response time for DNS lookups. See DNS Proxy Caching.

When this option is enabled, Content Gateway maintains a pool of virtual IP addresses that it assigns to the nodes in a cluster as necessary. See Virtual IP failover.

To see a complete description of the feature and an important list of restrictions, see Content Gateway support for IPv6.

See Working With Web DLP.

Enables registration with the on-box Web DLP components and the Forcepoint management server. See Registering Content Gateway with Forcepoint DLP.

Enables ICAP for use with Forcepoint DLP. See Configuring the ICAP client.

When SOCKS is enabled, Content Gateway communicates with your SOCKS servers. See Configuring SOCKS firewall integration.

See Integrated Windows Authentication.

When LDAP is enabled, users are authenticated by an LDAP server before they are allowed access to content.See LDAP authentication.

When RADIUS is enabled, users are authenticated by a RADIUS server before they are allowed access to content. See RADIUS authentication.

See Legacy NTLM authentication.

When Rule-Based Authentication is enabled, users are authenticated based on the parameters of the rule that they match. Rule-based authentication supports multiple realm, multiple domain, and other user authentication scenarios. See Rule-Based Authentication.

Select Single Node to run this Content Gateway server as a single node. This node will not be part of a cluster.

Select Management Clustering to activate management clustering mode. The nodes in the cluster share configuration information and you can administer all the nodes at the same time.

Specifies the interface on which Content Gateway communicates with other nodes in the cluster. For example, eth1.

See Changing clustering configuration.

See Changing clustering configuration.