Bypassing the Fiddler Everywhere proxy


Product Fiddler Everywhere
Product Version 1.0.0 and above


Q: I would like certain services, client applications, or specific endpoints to bypass the Fiddler Everywhere proxy and directly use the upstream proxy. How can I achieve that?

Q: An HTTPS service stopped working due to certificate pinning/SSL errors. How can I prevent that services from going through the Fiddler proxy?

Q: The iTunes on my iOS device is not working when Fiddler Everywhere is being set as a proxy. How to resolve that issue?

Q: I am using a service that pollutes my Fiddler Everywhere captured traffic. How to prevent this traffic from being caught from Fiddler Everywhere in the first place?


All the described issues above have a common solution - bypassing Fiddler so that the specific application endpoints use the default connection directly. As a result, any request to these endpoints will go straight through the upstream proxy, effectively bypassing Fiddler, and they won't use the Fiddler Everywhere certificate. The immediate effect is that Fiddler Everywhere won't capture traffic from the bypassed endpoints. Still, at the same time, the bypassed services will continue to work while using the default internet connection.

Proxy Bypass List

  • Open Fiddler Everywhere on the host machine and go to Settings > Connections.

  • In the Bypass Fiddler for URLS that starts with: field, add the endpoints that you would like to bypass, separated by a comma: Example for bypassing the Apple endpoints (for system services that are using certificate pinning)

    *, *, *

    Example bypass list

  • Click Save to persist the change.

Add to Bypass List

You can add domains to the bypass list on-the-fly while you are actively capturing.

  • Open Fiddler Everywhere and start capturing traffic.

  • Select a session that uses the domain which you would like to bypass.

  • With the session selected, open the context menu and choose Bypass > Add to bypass list.

Add to bypass list