Debug problem analysis for visual studion multiple virtual sites using Fiddler

  • 2020-06-01 09:36:27
  • OfStack

1: localhost. And The behavior of URL is not 1

The problem of not being able to go through the local agent is not an BUG problem, which is explained by Microsoft. It is due to the fact that the IE browser and the NET framework do not go through the agent for local requests, so Fiddler cannot detect the data. So add the dot symbol to the local address, and this brings up the problem that URL does not behave 1.

If we take the current Context.Request.URL, we will find that the system will automatically ignore the. Symbol in the address, which brings us the problem of no 1 for the URL code.

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

Filddler Option Enable IPV6 cancelled.

3: modify Custom Rules to bring URL behavior is not 1

Must be employed to solve the problem of 1, Custom Rules, information about corresponding: http: / / fiddler2 com documentation/KnowledgeBase/FiddlerScript/ModifyRequestOrResponse

For the two virtual sites in my solution, I would change the policy for Fiddler as follows:

if ("aaa:22222") {"";

if ("aaa:22222") {"";

Of course, this solution does not mean that aaa, URL, has been obtained, but localhost. In other words, there is still a problem that URL does not behave properly

4: set the site as "Use Local iis web server"

The debugging site set up in VS is not development server, but IIS, where URL is entered as the IP address of the machine, such as: Well, all this 1 cut, you can only blame the IE agent for not going to the local address. Since we know that Fiddler1 is on, we are actually setting up our own agent for IE.

Related articles: