Fiddler--autoresponder

Autoresponder supports the creation of rules that can be triggered automatically when responding to requests, and a common example is to return previously captured responses without requiring access to the server.

Popular point is that it can not access the server, so that the sending request to get its own set of responses.

Is the Autoresponder interface:

First, Part I

Enable rules check box: Controls whether Autoresponder is activated.

Unmatched Requests Passthrough: Controls what happens when the session does not match any given rule. If selected, mismatched requests are sent to the server normally, and if the item is unchecked, the mismatched request will receive a 404 response.

If you are sending a conditional request that contains a request header If-none-match or if-modified-since, you will get a 304 not Modified response.

For example, Fiddler captures the first 4 sessions, tick unmatched requests passthrough,replay four sessions, get 5th to 8th session, from the response results can be seen, the mismatch of the request sent, The normal response is obtained;

Do not tick unmatched requests Passthrough,replay First four session, get 9th to 12th session, mismatched request (non-conditional request), response is 404.

Enable Latency: Controls whether a request that matches a rule is executed immediately or the number of milliseconds specified in the Latency field is deferred. The latency field appears in the list only if this option is checked.

Second, Part Two

"If Request matches ...": Determines whether the received request matches the rule; the check box in front of the field indicates whether the rule is valid when checked;

"The Respond with ...": After a successful match, the action to be taken or the local file is returned;

Select a session and click the "Add Rule" button to add a rule to the list:

Of course, you can add a rule directly by clicking "Add Rule" without selecting the session.

After selecting the rule, you can modify the information in the Rule editor and click the "Save" button to save the information;

Select more than one rule to use the same response for these selected rules:

Iii. Specifying matching Criteria

In the second part, we can see the generated rules, preceded by "EXACT:" in the address. Specifying a prefix before a condition makes it easier and quicker to match to the session.

*: matches all received requests;

Specifies the prefix not:, matching the URL does not contain the given string of the request, the match case is not sensitive.

As can be seen, the URL does not exist in the "General" string, the response will return the specified file;

Specifies the prefix exact: Match case sensitivity is required.

Specify the prefix regex: to perform a regular match on the URL. An expression is passed. NET regular expression engine to match.

Iv. Assignment of Actions

You can see the following options in the Action input box:

Resources:

1. Fiddler Official documents: Http://docs.telerik.com/fiddler/knowledgebase/autoresponder

2, "Fiddler Debugging authoritative Guide"

Category: Fiddler

Fiddler--autoresponder