Seagate ST3300655LC Manual de usuario descargar pdf (Pagina 51)

SGOS 4.2.x

❐ Do not use existing Gateway Proxy or Reverse Proxy as a Concentrator Proxy.

❐ SOCKS Compression and HTTP Compression can be simultaneously active on

Concentrator Proxy with certain caveats listed below.

❐ Do not enable other functions that require large memory allocations on Concentrator

Proxy, such as:

• HTTPS termination/origination.

• HTTP decompression.

• Policy for page transforms, response data and apparent data type triggers.

❐ Do not enable other high CPU intensive applications, such as:

• HTTPS termination/origination.

• Spyware policy.

❐ Implement Page transforms and Spyware policies on the Gateway Proxy ( not the

Concentrator Proxy).

❐ Implement HTTPS termination/origination on the Reverse Proxy ( not the

Concentrator Proxy).

❐ The same Branch Proxy can be used for SOCKS Compression and other protocols, such

as HTTP.

❐ Blue Coat recommends that the Branch Proxy use the Concentrator Proxy as the HTTP

Proxy for forwarding HTTP traffic (not as SOCKS Proxy).

❐ The ProxySG does not support load balancing across SOCKS gateways.

❐ To compress Microsoft Outlook traffic, the ProxySG in the branch office must be in line

as a bridge. Because of dynamic traffic, you cannot use an L4 switch or a WCCP router

to intercept RPC services.

❐ Verify duplex settings are compatible in bridged deployments (in branch offices).

❐ Specifying the ports that intercept the CIFS/printing protocol: In a deployment where

one group of CIFS/printing services listens on both ports 139 and 445 and another

group of CIFS/printing services listens only on port 139, configure the branch

ProxySG to only intercept port 139; do not configure to intercept both ports 139 and

445. Otherwise, the port-139-only services will break. This presents the limitation that

when clients choose to use port 445, that content is not compressed because 445 traffic

is not intercepted.

Bridging

❐ When a ProxySG is deployed inline as a bridge, it intercepts traffic (such as HTTP Port

80 traffic) from both inside (Intranet) and outside (Internet). This makes the ProxySG

an Open Proxy unless it is explicitly configured to deny connections from the outside.

If this is not intended, you must create explicit policy rules to only proxy connection

from the inside.

❐ The PCAP bridging filter does not work in software bridge implementation.

(B#53918a)

1 2 ... 46 47 48 49 50 51 52 53 54 55 56 ... 61 62

Sin comentarios

Seagate ST3300655LC Manual de usuario Pagina 51