One of the most powerful features of the Fiddler Everywhere client is the Auto Responder - a tool for mocking server responses and simulating various real-life scenarios. With Auto Responder, you can create rules, which will automatically trigger to a specific request (that covers the criteria set in the rule). Mocking a server response is as easy as setting as enabling AutoResponder, setting a rule, and executing the request (that will trigger the rule).
To create and test your first Auto Responder rule follow these steps:
Open the Fiddler Everywhere client and switch the Live traffic to Capturing mode.
Select the Auto Responder tab and create your rule.
In the MATCH field, enter your match criteria. For this example, in the lines below, you will find a simple rule that matches ALL requests ending with PNG (the rules are created while using regular expressions).
regex:(?inx).+\.png$ #Match strings ending with PNG
The following basic example is creating a MATCH rule that will modify all requests that are ending with PNG. In most cases, you would like to mock a response from a request against a specific host. For that case, you could use the EXACT match. See more examples for creating different MATCH conditions.
In the ACTION field, enter the desired action. For this example, in the lines below, you will find a simple action that will drop everything corresponding to the MATCH criteria.
See more examples for creating actions
Add the rule to the Auto Responder rules list via the Add to Queue button.
Enable the Auto Responder and each rules that you need to execute.
Once the Auto Responder is turned on (via Enable AutoResponses), the activated rules apply for all incoming/outgoing traffic. If a session does not match any of the specified rules, the Fiddler Everywhere client will generate an
HTTP/404 Not Foundresponse. In case, you want unmatched requests to be sent generally to the servers, then activate the Unmatched Requests Passthrough option from the toolbar.
Open the application (e.g., a browser) and execute the request. As a result, if the request contains PNG images, they will be dropped. You have just tested a website against a scenario where the user has disabled all photos.