Above ( https://blog.csdn.net/qq_36662437/article/details/104874056 in) have been introduced Fiddler principles and software interface. This paper capture process for Fiddler's.
Fiddler HTTP request to fetch.
Fiddler capture is the most basic applications to this blog, for example, after starting Fiddler, enter in your browser https://blog.csdn.net/qq_36662437 After pressing Enter, the web session interface Fiddler's captured HTTP request is shown below:
A detailed description of each field already explained, it will not be described here. Note that the icon is the # column, each corresponding to different types of icons that represent specific types include:
Also, note that the host field of the request. You can see the response from multiple subdomains www.csdn.net, indicating in the architecture of large sites, most require multiple subdomains, those subdomains may be used alone to cache static resources, but also may be responsible for media resources, is responsible for the data or statistics (such as pingback).
Right-click a request them. There may be selected operations: save (save information request message may be a request packet, response packet may be). For example, we saved a request header information is as follows:
Not just a single session, Fiddler also supports crawling to save all the session (and supports import), which for suspicious requests to crawl and then save, and at any time after the analysis of these requests is helpful.
If you want to re-send certain request, you can select these requests, and then click on the toolbar reply. Can be selected to resend these requests.
Left-click a single HTTP request, the following information can be seen in the panel on the right tab:
1. Statistic。
Performance and other data about the HTTP request analysis:
We can see from some of the basic performance data: such as DNS resolution time consumption is 8ms, settling time TCP / IP connection consumption is 8ms and so forth.
2. Inspectors。
Is divided into two parts, upper half is a part of the request header, the lower half is part of the response header. For each section, a plurality of different formats to view the contents of each request and response. JPG format ImageView you can see the picture, HTML / JS / CSS use TextView can see the content of the response. Raw tab to see the original line with standard HTTP request and response headers. Auth you can view information about the authorization and Authorization of Proxy-Authorization. Cookies can see the tag set-cookie header information in the cookie and the response to the request.
3. AutoResponder
Fiddler one of the more important and more powerful features. A request may be used to intercept and redirect to the local resources, or use the built-in response Fiddler. Server-side code can be used to debug without modifying the server code and configuration, because the interception and redirection actually accesses the local file is built or obtained response of Fiddler. After checking allow autoresponser and set rules (in this embodiment, a rule is http://blog.csdn.net/ohmygirl intercept the request to the local file layout.html), as shown in FIG.
Then visit http://blog.csdn.net/ohmygirl in your browser, the actual result is:
This happens to be the contents of the local layout.html, indicating that the request has been successfully intercepted locally. Of course, you can use the built-in response Fiddler. The figure is supported by Fiddler to intercept redirection way:
Therefore, if you want to debug a script file servers, can intercept the script to the local after local finished modifying the script, and then modify the contents of the server, which can guarantee, try to go on debugging in a real environment, so as to minimize the possibility of bug occurred.
Not only is a single url, Fiddler way to support multiple url match:
I. characters match
As example can match http://www.example.com and http://example.com.cn
II. Exact match
EXACT showing exact match to the beginning, as example above
EXACT:http://blog.csdn.net/ohmygirl
III. Regular Expression Match
With regex: beginning, use regular expressions to match the URL
Such as:?.. Regex :( insx) * \ (css | js | php) $ express matches all css, js end, php url request
4. Composer。
The fiddler in the old version is called request-builder as the name implies, you can build the appropriate request, there are two common ways to build request:
After url (1) Parsed input request can be executed, you can also modify the corresponding header information (such as adding a common accept, host, referrer, cookie, cache-control header, etc.) after execute.
Common applications of this feature are: "brush-vote" (not a ticket !!), as refreshes visited pages (based on moral and security reasons, if you really go brush votes, brush visits, this blog is not responsible)
(2) Raw. Use HTTP headers to build http request. Similar to the previous. Not much narrative
5． Filter
Fiddler Another more powerful. Fiddler provide a multi-dimensional filtering rules, enough to meet the daily needs of development and debugging. Illustrated as follows:
Filter rules are:
a. host and filtration zone. Filter can display only intranet or the internet HTTP request
You can select specific domain HTTP request
b client process:. can capture request specifies process.
This request is useful for debugging a single application.
Other more settings you can refer to the official documentation of the fiddler.
----------------
Disclaimer: This article is the original article CSDN bloggers "ohmygirl", and follow CC 4.0 BY-SA copyright agreement, reproduced, please attach the original source link and this statement. .
Original link: https: //blog.csdn.net/ohmygirl/article/details/17849983
