Basic

Configuration Options > My Proxy > Basic

Basic

Help | Content Gateway | Version 7.7.3

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.

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

Proxy Name

Specifies the name of your Content Gateway node. By default, this is the hostname of the machine running Content Gateway.

If this node is part of a cluster, this option specifies the name of the Content Gateway cluster. In a Content Gateway cluster, all nodes must share the same name.

Alarm email

Specifies the email address to which Content Gateway sends alarm notifications.

Features

Protocols: FTP

When this option is enabled, Content Gateway accepts FTP requests from FTP clients.

If this option is changed you must restart Content Gateway.

Protocols: HTTPS

Enables/disables processing of HTTPS requests (encrypted data) with SSL Manager. After selecting HTTPS On, you must provide additional information on the Configure > Protocols > HTTPS page and on the Configure > SSL pages. See Working With Encrypted Data.

Networking: WCCP

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.

If you change this option, you must restart Content Gateway.

Networking: DNS Proxy

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.

Networking: Virtual IP

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.

Networking: IPv6

When this option is enabled, Content Gateway provides limited support for IPv6.

Support is provided for explicit proxy only.

IPv6 addresses can be used on any dual stack Ethernet interface that services client and/or Internet traffic.

IPv4 addresses must be used to communicate with all TRITON components.

See Content Gateway Version 7.7.3 support for IPv6.

Networking: Data Security

Enables a connection to Websense Data Security. There are 2 options:

Automatic registration with the Data Security Management Server (must be version 7.7)

ICAP communication to a remote Data Security Suite deployment (may be version 7.1, or earlier)

See Working With Websense Data Security.

If you change this option, you must restart Content Gateway.

Networking: Data Security: Integrated
on-box

Enables registration with the on-box Data Security components and the Data Security Management Server. See Registering and configuring Data Security.

Networking: Data Security: ICAP

Enables ICAP for use with Data Security Suite. See Configuring the ICAP client.

Security: SOCKS

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

If you change this option, you must restart Content Gateway.

Authentication: None

Content Gateway supports several types of user authentication.

When this option is selected, the proxy does not perform user authentication. This is the default setting.

Authentication: Integrated Windows Authentication

When Integrated Windows Authentication (IWA) is enabled, users are authenticated by IWA before they are allowed access to content.

See Integrated Windows Authentication.

If you change this option, you must restart Content Gateway.

Authentication: LDAP

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

If you change this option, you must restart Content Gateway.

Authentication: Radius

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

If you change this option, you must restart Content Gateway.

Authentication: Legacy NTLM

When legacy NTLM (NTLMSSP) is enabled, users in a Windows network are authenticated by a Domain Controller before they are allowed access to content.

See Legacy NTLM authentication.

If you change this option, you must restart Content Gateway.

Authentication: Multiple Realm Authentication

Enables or disables multiple realm authentication. Multiple realm authentication supports environments that have multiple domains that do not share trust relationships, thus requiring that specific users be authenticated by specific domain controllers.

See Multiple realm authentication.

If you change this option, you must restart Content Gateway.

Authentication: Read authentication from child proxy

Enables or disables the reading of X-Authenticated-User and X-Forwarded-For header values in incoming requests. This option is disabled by default.

Enable this option when Content Gateway is the parent (upstream) proxy in a chain and the child (downstream) proxy is sending X-Authenticated-User and X-Forwarded-For header values to facilitate authentication.

Authentication: Send authentication to parent proxy

Enables or disables the insertion of X-Authenticated-User header values in outgoing requests. This option is disabled by default.

Enable this option when Content Gateway is the child (downstream) proxy in a chain and the parent (upstream) proxy wants X-Authenticated-User values to facilitate authentication.

Clustering

Cluster: Type

Specifies the clustering mode:

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.

For complete information about clustering, see Clusters.

If you change this option, you must restart Content Gateway.

Cluster: Interface

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

Node configuration information is multicast, in plain text, to other Content Gateway nodes on the same subnet. Therefore, Websense recommends that clients be located on a separate subnet from Content Gateway nodes (multicast communications for clustering are not routed).

On V-Series appliances, P1 (eth0) is the recommended interface. However, you may also use P2 (eth1) if you want to isolate cluster management traffic.

See Changing clustering configuration.

If you change this option, you must restart Content Gateway.

Cluster: Multicast Group Address

Specifies the multicast group address on which Content Gateway communicates with its cluster peers.

See Changing clustering configuration.

Cluster: SSL Manager Configuration Server