Red Hat DIRECTORY SERVER 2.0 - GATEWAY Instalační příručka

Deploying with Websense Content GatewayWebsense® Content Gateway is a high-performance Web proxy that provides real-time content scanning and Web site

 custom internal applicationsMany of these programs are not developed with proxy compatibility in mind. For a successful transparent proxy deployment

A router may also use Layer 2 (L2), which does not use GRE. Websense recommends the use of L2 if the router supports it. With L2 redirection, Content

A comparison of how some activities are handled in explicit and transparent proxy deployments appears in the following table:Special Deployment Scenar

switching options. This section summarizes some possibilities for highly available Web proxy deployments.Using explicit proxyAs previously mentioned f

Active/ActiveIn an active/active configuration with 2 proxies, more than one virtual IP address is assigned to the virtual IP address pool. At any poi

With load balancingA load balancer is a network device that not only distributes specific client traffic to specific servers, but also periodically ch

Using transparent proxyIn a transparent proxy deployment for high availability, traffic forwarding may be accomplished using a Layer 4 switch or a WCC

specific proxy. In this scenario, WCCP distributes client requests based on the proxy server’s IP address, routing traffic to the proxy most likely to

Websense Content Gateway is downstreamA simple deployment has Websense Content Gateway as the downstream proxy, closest to the client. In this scenari

If the third-party proxy can send the X-Forwarded-For header but not the X-Authenticated-User header, the following step is also required: Deploy an

User authenticationHTTPS content inspectionHandling special casesExplicit proxy deploymentTransparent proxy deploymentHighly available Web proxyIn a p

If you want to exclude SLL traffic from the parent proxy and tunnel the traffic directly to the origin server, enable the Tunnel Requests Bypass Paren

Set Websense Content Gateway as the forwarding host (in the Blue Coat Management Console Configuration tab, Forwarding > Forwarding Hosts). In the

Content Gateway to read the X-Forwarded-For and X-Authenticated-User headers sent by the downstream ISA server. Two versions of the plug-in are availa

Transparent proxy deployment includes either a Web Cache Control Protocol (WCCP)-enabled router or Layer 4 switch to redirect traffic, as described be

unless the issue is deemed a Red Hat Enterprise Linux-specific issue, at which point you must contact Red Hat directly for assistance.  RPM compat-li

Another type of clustering supported by the Content Gateway is cross-cache clustering, a complex proxy deployment that allows any node in a proxy clus

User authenticationAuthentication is the process of verifying a user via a username and password. User authentication may be configured on Websense Co

servers. Rules may be defined for both types of authentication realms, but only one method (NTLM or LDAP) can be active at any time. See Websense Cont

IP addresses for which SSL decryption is not performed. See the chapter titled Scanning and SSL Bypass Options in TRITON - Web Security Help for infor

For explicit proxy deployment, individual client browsers may be manually configured to send requests directly to the proxy. They may also be configur