About the Explicit Proxy

In a standard proxy configuration, the Firebox transparently proxies and inspects client connections to servers. In an Explicit Proxy configuration, the Firebox accepts direct requests from clients, completes a DNS lookup, connects to specified servers, and then gets the information on behalf of the client. In this configuration, the client is specifically configured to use the Firebox as a proxy server.

If your current network environment uses an explicit web proxy server for HTTP traffic, you can replace your current proxy server with a Firebox without infrastructure reconfiguration.

You can use the Explicit Proxy to support these primary proxy configurations:

The Explicit Proxy on the Firebox sends traffic over TCP port 3128.

You can use the Explicit Proxy to monitor and control connections from Chromebooks. For more information, go to the Chromebook with WatchGuard Explicit Proxy Integration Guide on the WatchGuard Technology Partners page.

Client Configuration and Proxy Automatic Configuration Files (PAC)

When you use the Explicit Proxy for web traffic, you must configure your client web browsers to use the Firebox address as the proxy server. You can manually configure your client web browser with the address of the Firebox or use proxy automatic configuration (PAC) methods to distribute the proxy configuration to all your clients.

For more information about PAC files and client configuration, go to Explicit Proxy: PAC Files and Client Web Browser Configuration.

Explicit Proxy Log Messages and Dimension

Log messages for the Explicit Proxy are included with the other HTTP proxy traffic log messages in Dimension Log Manager and reports.

Configure the Explicit Proxy

Related Topics

Explicit Proxy: HTTP Web Proxy

Explicit Proxy: FTP over HTTP

Explicit Proxy: HTTP CONNECT Tunneling