How to share and maintain multiple Fiddler scripts?

I have many customizable and independent FiddlerScript extensions that I want to maintain and share with colleges.

Currently (and this is the only way I know) all these parts of the script are in the% USERPROFILE% \ Documents \ Fiddler2 \ Scripts \ CustomRules.js file, I don’t know how to create one script file for each functionality. In addition, most extensions are distributed through the script file because they require code in different event handlers (e.g. OnBeforeRequest ) and define custom parameters, such as flags. This makes it difficult to identify all parts belonging to one extension.

Although I could copy the entire CustomRules.js file, it would be unpleasant if all recipients of the file re-enable all custom add-ons, each of which changed the time.

Is there a way to create a separate script file or encapsulate extensions in closed blocks (i.e. attach to events like OnBeforeRequest outside the static function OnBeforeRequest(oSession: Session) )?

The solution should work with vanilla Fiddler, without any changes to Fiddler itself. (Re-) creating all the necessary extensions, since .NET extensions are not a working solution for me.

+7
fiddler
source share
1 answer

There is currently no, there is no way to do this, although people request this functionality from time to time, and features of this nature may possibly be added at some point in the future. At the moment, it is expected that functionality useful enough for sharing is useful enough to compile into the Fiddler Extension assembly.

You can find this extension: https://github.com/vcsjones/FiddlerScriptCSharp is interesting as it offers the types of features that you describe using C # as the JScript.NET scripting language.

+3
source share

All Articles