icon-zapp.svg
Client Connector

Using Fiddler with Zscaler Client Connector

To use the Telerik Fiddler application with Zscaler Client Connector, you must configure Zscaler Client Connector to use a PAC file to point to a specific port. Then, you must ensure that Fiddler is listening to that port.

At a high level, the flow of traffic should be: Browser > Fiddler > Zscaler Client Connector > Destination Page.

To learn more, see Best Practices for Using PAC Files with Zscaler Client Connector.

Configuring Zscaler Client Connector and Fiddler

For more information on Fiddler, refer to the Telerik documentation. The version used for the following steps is Fiddler 5.0.20182.28034.

To use Fiddler with Zscaler Client Connector:

  • To learn more about creating a custom PAC file, see Writing a PAC File.

    Create a custom PAC file with the following return statement:

    return "PROXY 127.0.0.1:<Port for Fiddler>; PROXY ${ZAPP_LOCAL_PROXY};";

    You must add the port to the return statement. For example, if you choose port 8888, then the return statement is as follows:

    return "PROXY 127.0.0.1:8888; PROXY ${ZAPP_LOCAL_PROXY};";

    You can host the PAC file in the Zscaler Admin Portal. To learn more, see Adding a Custom PAC File to the ZIA Admin Portal.

    If you want to debug on a local web server, the browser’s PAC file may ignore the request for 127.0.0.1. As a workaround, create a host file entry pointing to 127.0.0.1(e.g., 127.0.0.1 server.local).

    Close
  • This step is not required if you are using Fiddler to automatically configure the system proxy, as Fiddler manages the system proxy settings.

    Create a new forwarding profile or update an existing one, and then add the custom PAC file.

    You must configure the forwarding profile with the following settings:

    • Select Tunnel with Local Proxy or Tunnel mode for any application network (i.e., On Trusted Network, VPN Trusted Network, Off Trusted Network).

    If you have configured Fiddler to automatically populate system proxy settings, you must use Tunnel mode and not Tunnel With Local Proxy mode. This is because the Zscaler Client Connector enforces its own system proxy in Tunnel With Local Proxy mode.

    • For the Use Automatic Configuration Script field, click the checkbox and enter the custom PAC URL.

    The PAC URL in this example is http://pac.zscaler.net/safemarch.net/fiddler.

    Adding a custom PAC file to a Zscaler Client Connector forwarding profile

    Close
  • Create a Zscaler Client Connector profile or update an existing one, and then add the configured forwarding profile.
    The forwarding profile in this example is Fiddler.

    You must configure the app profile with the following settings:

    • The Rule Order must be 1.
    • The app profile must be enabled.
    • The Disabled Loopback Restriction switch must be enabled.

    Adding the forwarding profile to a Zscaler Client Connector profile

    Close
  • To configure Fiddler:

    1. Open the Fiddler application.
    2. Go to Tools > Options…

    Navigating to the Fiddler options menu to configure settings for Zscaler Client Connector

    1. In the Options window, click the Connections tab and do the following:
      • Fiddler listens on port: Enter the port that you configured in the forwarding profile PAC file.
        The port in this example is 8888.

    Configuring Fiddler to listen to the port from the Zscaler Client Connector forwarding profile PAC file

    1. Click the Gateway tab and do the following:
      • Manual Proxy Configuration: Select this option. In the first field, enter the following proxy string.
    http=127.0.0.1:<Zscaler Client Connector Port>;https=127.0.0.1:<Zscaler Client Connector Port>;ftp=127.0.0.1:<Zscaler Client Connector Port>;

    You must add the port that Zscaler Client Connector listens on to the proxy string. For example, if Zscaler Client Connector listens on port 9000, then the proxy string is the following:

    http=127.0.0.1:9000;https=127.0.0.1:9000;ftp=127.0.0.1:9000;

    Optionally, to debug on a local web server, enter Bypass list: <local>; in the second Manual Proxy Configuration field.

    Configuring Fiddler manual proxy configuration settings with the port Zscaler Client Connector listens on

    If you are using the Fiddler AutoResponder feature, the Accept all CONNECTs option must be disabled.

    1. Click OK.
    Close

After you finish the configuration for both Zscaler Client Connector and Fiddler:

  1. Enroll in Zscaler Client Connector if you have not already.
  2. When Internet Security for Zscaler Client Connector is ON, you can open and use Fiddler.

Ignore any errors that Fiddler displays during startup.

Related Articles
Implementing Zscaler Client Connector in No-Default Route EnvironmentsDomain Validation in Zscaler Client Connector for ZPA ApplicationsBest Practices for Zscaler Client Connector and VPN Client InteroperabilityZscaler Client Connector and Charles Proxy InteroperabilityZscaler Client Connector Processes to AllowlistAllowing Traffic to the ID Federation URL by Bypassing Zscaler Client ConnectorEnrolling Zscaler Client Connector Users When Using a ProxyUsing Fiddler with Zscaler Client ConnectorBest Practices for Using PAC Files with Zscaler Client Connector