The Umbrella User Guide Developer Hub

Welcome to the Umbrella User Guide developer hub. You'll find comprehensive guides and documentation to help you start working with Umbrella User Guide as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Manage Umbrella's PAC File

When configuring Umbrella's secure web gateway (SWG), you have several choices as to how you can send web traffic to Umbrella. One of those choices is to integrate a proxy auto-config (PAC) file URL for the browser you will be using to reach destinations. Once integrated into your system, all traffic through that browser is redirected to Umbrella's secure web proxy. When deploying Secure Web Gateway with a PAC file, Umbrella DNS policies will not be enforced for traffic generated in the web browser. DNS policies will still apply to non-web browser traffic which bypasses the PAC file.

Note: PAC file downloads and usage are limited to fixed networks registered in Umbrella. PAC files are not supported for roaming computers or other connection mechanisms.

What's a PAC file?

A proxy auto-config (PAC) file is used to tell a browser which proxy server it must use to fetch a URL.

For the most part, integrating Umbrella's PAC file into your system so that all browser-based traffic is proxied is a simple cut and paste procedure. There may, however, be occasions when you are required to customize the PAC file before integrating it into your system. For more information about deploying and customizing a PAC file, see:

Note: Microsoft has deprecated PAC file support for the file:// and ftp:// protocols in Windows 10 on Edge. Hosting the PAC file on the local machine will not work on this browser. For more information, see Windows 10 does not read a PAC file referenced by a file protocol.


Test SSL Decryption < Manage Umbrella's PAC File > Deploy Umbrella's PAC File for Windows

Updated about a month ago

Manage Umbrella's PAC File


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.