Unplanned
Last Updated: 16 Sep 2026 08:48 by ADMIN
Leonard
Created on: 16 Sep 2026 08:46
Type: Feature Request
0
Add an automated, non-UI way to manipulate the Fiddler Everywhere configuration
In my company we have been using Fiddler Classic for years now.

We were using Fiddler Classic within VM environments, where the Fiddler settings were already preconfigured.

For this preconfiguration we were using a combination of automatically setting registry keys (e.g. for configuring the "Hosts to be skipped" for traffic capturing), automatic manipulation and replacement of the Fiddler script, and the usage of the "ExecAction" executable.

We would like a way to do all those configurations in an automated, non-UI way for Fiddler Everywhere as well.

For us the following things would need to be automatically configurable, for Fiddler Everywhere to cover the same use cases as Fiddler Classic does so far:

- Manipulating the list of "Hosts to be skipped" for traffic capturing

- Manipulating the maximum amount of sessions to be kept in the "Live Traffic"

- Exporting the Fiddler Root Certificate

- Enabling/Disabling HTTPS traffic capturing

- Enabling/Disabling the "System proxy" mode

- Enabling/Disabling the "Allow remote devices to connect" setting

- Adding/Removing Rules

- Enabling/Disabling existing Rules
1 comment
ADMIN
Nick Iliev
Posted on: 16 Sep 2026 08:48
Hello Leonard,



Thank you for the detailed background - it's very helpful to understand how you automated Fiddler Classic in your VM environments via registry keys, script replacement, and ExecAction. Fiddler Everywhere takes a different approach (no FiddlerScript/ExecAction equivalent), but it does offer a Managed App Configuration feature (Enterprise tier) that lets IT teams pre-configure the app without touching the UI, via Windows registry (HKEY_CURRENT_USER\SOFTWARE\Policies\Progress\Fiddler Everywhere, with HKEY_LOCAL_MACHINE taking precedence) or macOS defaults/MDM profiles (Jamf, Intune, etc.).

Here is how your list of requirements maps to what's available today:

  • Hosts to be skipped for traffic capturing — Partial: DefaultBypassList / DisableBypassListChange (proxy bypass list); DefaultNetworkCaptureList / DefaultNetworkCaptureFilterList (network-capture scope)
  • Max sessions kept in Live Traffic — Not supported
  • Exporting the Fiddler Root Certificate — Partial: CustomCACertificate / CustomCACertificatePrivateKey (push in a pre-issued CA; no export policy)
  • Enable/Disable HTTPS capture — Not supported
  • Enable/Disable System Proxy mode — Not supported
  • Enable/Disable "Allow remote devices to connect" — Supported: DisableAllowRemoteDevicesToConnect
  • Adding/Removing Rules — Not supported
  • Enable/Disable existing Rules — Not supported
  • Other policies available today that may still be useful for your locked-down VM scenario include DisableAnalytics, DisableCloud, DisableMCP, DisableAssistant, DisableSanitizationSettingsUpdate, and DefaultSanitizationSettings — full reference: Managed App Configuration.

As you can see, several of your requirements (session limits, HTTPS capture toggle, system proxy toggle, and rules management/import) aren't covered by the current policy set. We'd like to understand your use case in more depth and talk through possible enhancements or new configuration options/APIs that could close these gaps.

We'd like to propose a private call with our team - our Product Manager and a representative from the development team will join from our side. Would September 17th, or any time after September 23rd, work for you (we have some non-working days in our office in between)? Let us know your preferred date/time and time zone, and we'll send an invite.

Looking forward to hearing more about your setup.

 

Regards,
Nick Iliev
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.