If you want to filter the current Fiddler's packet capture (such as filtering out packet capture requests that are not related to the test project), then the powerful Filters filter can help you.
If you want to learn the Fiddler packet capture tool, here I recommend a set of videos for you. This video can be said to be the No. 1 Fiddler packet capture tool tutorial on the Internet at station B. At the same time, the number of online users reaches 1,000, and there are notes available. Receipt and technical exchanges with various great gods : click on the card at the bottom of the article'
https://www.bilibili.com/video/BV14g4y1H7vv/?spm_id_from=333.999.0.0Enter the Filters option page, check Use Filters to enable the filter.
Actions Description of four options:
Run Filterset now -- use the current filtering rules.
Load Filterset... -- Load (previously saved) filter sets.
Save Filterset... -- Save the current filtering rules (very practical, such as setting a set of filtering rules for each application test)
Help -- Enter fiddler online help.
Tips : The best way to master the following filtering rules is to watch and experiment.
1. Hosts filtering (commonly used)
- No Zone Filter - -- No zone filter is set.
Show only Intranet Hosts -- only show the internal Hosts, that is, filter out the Hosts of the external network. At this time, only the URL requests to the target server on the internal network are displayed.
Show only Internet Hosts -- Correspondingly, only hosts on the external network are displayed.
- No Host Filter - -- Do not set filter host IP conditions.
Hide the following Hosts -- Hide the Hosts entered into the text box below.
Show only the following Hosts -- Show only the Hosts entered into the text box below.
Flag the following Hosts -- The following Hosts are displayed in bold.
For example , if you only want to display requests from www.51ste.com, select Show only the following Hosts and fill in www.51ste.com in the input box below. At this time, even requests from http://51ste.com will be filtered out and cannot be displayed.
2. Client Process filtering (client process filtering, only filter/not filter the requests of which processes through configuration. It is not used much)
Show only traffic from -- You can specify which Windows process to display only the requests in, and all current Windows processes will be listed on the right.
Show only Internet Explorer traffic -- Show only requests made by IE.
Hide traffic from service host -- Hide traffic from service host.
3. Request Headers (filter based on request header information. Commonly used)
Show only if URL contains -- only display requests that contain the specified string in the URL (the string can be part of the URL, and multiple strings are separated by spaces (multiple means or, that is, as long as the URL contains any string, it will be display), which can be a regular or full URL).
Hide if URL contains -- Only hide the request that contains the specified string in the URL (the string can be a part of the URL, separated by spaces, and can be a regular or complete URL).
Flag requests with headers -- Flag requests with specific headers (i.e. bold). For example, I want to highlight the URL request with the token field in the header information, that is, I can check this item and enter: token
Delete request headers -- delete the Header field in the request. (It is very useful for testing, such as removing the token information in the URL, and judging whether the server has performed token verification)
Set request Header -- Add a header field in the URL request, corresponding to the previous one. Enter the field in front and the value in the end.
4. Breakpoints set breakpoints (rarely used, after all, you can set breakpoints through bpu, bpafter and rewriting rule js)
Break request on Post -- Set a breakpoint on a Post request.
Break request on GET with query string -- set a breakpoint for a GET request.
Break on XMLHttpRequest -- Set a breakpoint on Ajax requests.
Break response on Content-type -- Set a breakpoint for requests that successfully match the Content-Type header field in the response message.
5. Response Status Code (Filter based on URL request response status code, not used much)
Hide success(2xx) -- Hide URL requests with a response status code of 2xx, such as URL requests with a response status code of 200 will be hidden.
Hide non-2xx -- Hide URL requests whose response status code is not 2xx.
Hide Authentication demands(401,407) -- Hide authentication (response status code: 401 407) URL
request.
Hide redirects(300, 301, 302, 303,307) -- URL requests that hide redirects (response status codes are: 300 301 302 303 307).
Hide Not Modifield(304) -- Hide URL requests that are not cached status codes (304). Regarding the 304 request, you can see the detailed explanation of Fiddler's Replay function http://www.51ste.com/share/det-889.html
6. Response Type and Size (filter based on response type and packet size, less used)
Show all Content-Type -- Display all types of Content-Type requests, and Content-Type is the Content-Type field in the header information of the response result.
Show only IMAGE/* -- only show requests with a response type of image. (that is, respond to requests with Content-Type=IMAGE/* in the header, and * is a wildcard)
Show only HTML -- only display requests whose response type is HTML.
Show only TEXT/CSS -- Show only requests with a response type of TEXT/CSS.
Show only SCRIPTS -- Show only requests with a response type of SCRIPTS.
Show only XML -- Show only requests with a response type of XML.
Show only JSON -- Show only requests with a response type of JSON.
Hide IMAGE/* -- Hide all requests with an image response type.
Hide smaller than -- Hide requests with response results smaller than the specified size. (The size can be viewed in Transformer in the Response Result section of Inpsectors)
Hide larger than -- Hide requests that are larger than the specified size response result.
Time HeatMap Time's Heatmap
Block script files -- Blocks returning normal JS files.
Block image files -- Blocks normal image files from being returned.
Block SWF files -- Blocks the return of normal SWF files.
Block CSS files -- Blocks normal CSS files from being returned.
Tip: This function can test the display of the page when CSS, JS, etc. fail to load.
7. Response Header (Filter processing according to URL request response header information, less used)
Flag responses that set cookies -- mark (in italics) if there are cookies information in the response.
Flag responses with headers -- Flags requests with specific headers in the response (i.e. bold).
Delete response headers -- Delete the header field specified in the response message.
Set response header -- add the header field in the response. If you add Transfer-Encoding: chunked, fill in Transfer-Encoding in front and chunked in the back.