Static bypass rules

Support

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

Transparent Proxy and ARM > Interception bypass > Static bypass rules

Static bypass rules

Help | Content Gateway | Version 7.7.3

You can configure bypass rules to direct requests from certain clients or to particular origin servers around the proxy. Unlike dynamic bypass rules that are purged when you restart the proxy, these static bypass rules are saved in a configuration file.

You can configure 3 types of static bypass rules:

Source bypass, in which Content Gateway bypasses a particular source IP address or range of IP addresses. For example, you can use this solution to bypass clients who want to opt out of a caching solution.

Destination bypass, in which Content Gateway bypasses a particular destination IP address or range of IP addresses. For example, these could be origin servers that use IP authentication based on the client's real IP address. Destination bypass rules prevent Content Gateway from caching an entire site. You will experience hit rate impacts if the site you bypass is popular.

Source/destination pair bypass, in which Content Gateway bypasses requests that originate from the specified source to the specified destination. For example, you could route around specific client-server pairs that experience broken IP authentication or out of band HTTP traffic problems.

Source/destination bypass rules might be preferable to destination rules because they block a destination server only for those particular users that experience problems.

To configure static bypass rules, edit the bypass.config file (See bypass.config).

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

Transparent Proxy and ARM > Interception bypass > Static bypass rules