Problem Analysis of Using Fiddler to debug multiple visual studion virtual sites

1: The URL behavior caused by localhost. is inconsistent with 127.0.0.1.

The local agent cannot be used. The problem of local debugging failure is not a BUG. Microsoft has provided an official explanation, which is due to IE browser and.. NET Framework does not take proxy for local requests, so Fiddler cannot detect data. Therefore, adding a. symbol to the local address causes inconsistent URL behavior.

When the current Context. Request. URL is retrieved, the system automatically ignores the. symbol in the address, which leads to inconsistent URL encoding;

2: target machine actively refused it (the target address is actively rejected)

Enable IPV6 of Filddler Option is canceled.

3: modifying the inconsistent URL behavior caused by Custom Rules

Solve the problem in 1, must use Custom Rules, the relevant information corresponds to: http://fiddler2.com/documentation/KnowledgeBase/FiddlerScript/ModifyRequestOrResponse

My solution corresponds to two virtual sites. The change policy for Fiddler is as follows:

If (oSession. host = "aaa: 22222 "){
OSession. host = "127.0.0.1: 22222 ";
}

If (oSession. host = "aaa: 22222 "){
OSession. host = "127.0.0.1: 22222 ";
}

Of course, this solution does not mean that the URL aaa is obtained, but localhost. That is, the URL behavior inconsistency still exists.

4: Set the site to "Use Local iis web server"

In VS, the debugging site is not the development server, but IIS. Enter the URL as the local IP address, for example, http: // 192.168.80.1 /. Well, all of this can only blame IE for having no proxy for the local address. Because we know that when Fiddler is enabled, it is actually set to use its own proxy for ie.