1. Filter unwanted sites

Filters are useful when we capture a bunch of packets, many of which are not needed and interfere with our view. They can hide unwanted domain names or use regex to match urls that need to be captured or hide urls

Hide some links based on the URL content

For example, to hide image links, set the hide If URL in request Heasers

REGEX:(? insx)/[^\?/]*\.(ico|jpg|png|gif|bmp|wav)(\? . *)? $Copy the code

According to the domain name | | hidden

You can display or hide certain domain names. The following uses hiding as an example

In the second option of Hosts, select Hide the following Hosts, and then enter the domain names that you want to Hide, separated by semicolons (;). This will make your screen much clearer



After configuration, don’t forget to click the Actions button run Filterset Now in the upper right corner

Resend request & breakpoint

Testing an interface may require repeated testing, so do you repeat the previous scenario each time? The answer is no

Method 1: First select the Composer option under the menu bar, then select a request that needs to be tested again in Filddler and drag it to the Composer window. At this time, all the content related to the request will be copied. We can change the parameters here and click execute directly



Method 2: If you simply want to send the request again, if you need to change the parameters, you can select the request, directly click the menu on Replay ok

Method 3: Select Reissue and Edit and the request will be broken. At this time, you can modify the page entry parameter in the TextView. After the modification is complete, click Break onResponse and the request will be broken when the request comes back. At this point, the value of response can be modified. The advantage of this is that we do not need to create data in order to reproduce a scene, but only need to change the entry and exit parameters to achieve the goal

Method 4: Type bpu XXX in the bottom black box on the Fildder console

XXX is the interface link that needs a breakpoint. When the packet is captured and the URL matching this link is captured, the breakpoint will be broken

When the interrupt point is no longer needed, the console needs to enter the BPU

3. Link local files for debugging

If there is a bug in the production environment, it is not very convenient for us to debug, and after the modification, we cannot determine whether the code is ok in the production environment, then this feature can help us

Select AutoResponder, Add Rule, as shown, with the production link above and the local code address below to test the local code in production

regex:(? inx)^Copy the code



4. Text Wizard

This function I also recently found, we captured the link, or in other places to see links or content are a lot of enCode after, then deCode how to do? This can be tricky to write using a console or other online tool, but the powerful Fiddler tool already provides you with a handy way to convert text, as shown in the picture below



5. Save captured packet data

This function is useful for testing. For some problems that cannot be reproduced 100%, when the captured packet data is obtained in a certain packet capture, it can be saved for future problem search, or sent to the developer to import Fiddler through File→Load Archive, so that there is no need to worry about data clearing