Rules Presets / Modify Traffic

Modifying Response Bodies

One of the most common testing practices is quickly changing a piece of code or a resource and rebuilding it to visualize the results. This can be time-consuming if the rebuild also involves deploying your application online.

With Fiddler Everywhere, you can quickly modify the content of the received HTTP responses by inserting, substituting, or entirely changing the targeted entries.

Creating an "Insert HTML" Rule

Create an "Insert HTML" rule by setting the following actions through the Rules Builder.

  1. Create a matching condition that uses the "When all these conditions are met any number of times" pattern.

  2. Match by a URL that uses a string value to match the desired URL. For example: example.com.

  3. Create an Update Response Body action and use the Find and Replace string modifier.

This sample Fiddler rule finds a selected H1 HTML element and inserts a logo before it.

Creating "Insert HTML" rule

Once the rule is created, enable the Rules tab, toggle the rule switch, and start capturing traffic.

Activating the "Insert HTML" rule

Download a ready-to-use "Insert HTML" rule as a FARX file, which you can import through the Rules toolbar.

Creating an "Insert HTML (ReGex)" Rule

Create an "Insert HTML (RegEx)" rule by setting the following actions through the Rules Builder.

  1. Create a matching condition that uses the "When all these conditions are met any number of times" pattern.

  2. Match by a URL that uses a string value to match the desired URL. For example: example.com.

  3. Create an Update Response Body action and use the Regular expession modifier.

This sample Fiddler rule finds the H1 HTML element using the following regular expression <div[\n\r\s\S]*?<h1> and then inserts a logo before it.

Creating "Insert HTML" rule

Once the rule is created, enable the Rules tab, toggle the rule switch, and start capturing traffic.

Activating the "Insert HTML" rule

Download a ready-to-use "Insert HTML via regex" rule as a FARX file, which you can import through the Rules toolbar.

You can identify different parts of the same response by combining multiple actions in a single rule. Actions are executed from top to bottom with the top actions or rules having the higher priority. Any final action immediately prevents the execution of all other actions and rules that are with lower priority. If there are no final actions, you can execute all actions from top to bottom, which means that you can overwrite the same part of the modification by actions placed lower in the queue.

See Also

In this article
Related articles
Improve this article