Proxy bypass
Proxy bypass sites are destinations that users can access either directly, or through an alternate (third-party) proxy, without going through the cloud service. For example, organizational webmail sites and system traffic, like Microsoft and antivirus updates, should be added to the bypass list.
- For users with the Neo or Direct Connect endpoint, bypass destinations are not analyzed by the cloud service.
- For users whose traffic is sent to the cloud service via PAC file, including users of the Proxy Connect endpoint, bypass destinations are added to the policy PAC file.
- By default, the PAC file excludes all non-routable and multicast IP address ranges; so if you are using private IP address ranges defined in RFC 1918 or RFC 3330, you need not enter these.
- Browsers configured to use the policy’s PAC file automatically use the cloud service, but bypass it for the specified destinations.
Any destinations that you add to the Proxy Bypass table apply only to the selected policy. To add bypass destinations that apply to all policies, use Proxy Bypass tab of the page.
To define bypass destinations: