What if fiddler does not capture traffic?

Fiddler2 is a powerful tool for debugging web pages, but it is due to the fact that fiddler2 cannot capture HTTP requests. Looking at the empty Fiddler, we often have to worry about it. As a web debugger, I have used fiddler in various environments and shared some small experiences.

1, localhost/127.0.0.1/[: 1]

Fiddler cannot capture the traffic of the above three addresses because the traffic of the ie hard Code addresses does not go through the proxy. (It is said that ie9 and later versions fix this issue without verification ). To capture the traffic of localhost, you can simply change the localhost in the URL to the computer name of this server.

2. pure IPv6 environment

In a pure IPv6 environment, Fiddler cannot catch traffic with the default settings. In tool-> fiddler options, (1) Enable IPv6 on the General tab (2) allow remote computers to connect on the Connections tab, and then restart Fiddler.

3. Naturally, proxy systems cannot be bound, such as some server systems.

You can convert fiddler config into a reverse proxy.

(0) in tool-> fiddler options, check allow remote computers to connect on the Connections tab and restart Fiddler.

(1) Run regedit

(2) Create a New DWORD in hkcu \ Software \ Microsoft \ fiddler2 named "reverseproxyforport"

(3) set the DWORD value to the port number of the website you want to debug. The default value is 80. Note: The default value of DWORD is 16 bits. For example, if port 80 is used, it must be set to a 10-bit 80, that is, the 16-bit 50.

(4) Restart fiddler

(5) Enter http: // 127.0.0.1: 8888/in the browser/