Using Fiddler to debug the problem analysis of visual Studion multiple virtual sites _ practical Tips

1:localhost. and 127.0.0.1. URL behavior Inconsistent

Unable to walk local agent, the problem that cannot be debugged locally is not a bug, Microsoft Official has explained, this is from IE browser and the. NET Framework for local requests is not agent, so fiddler cannot detect data. Then add the. symbol to the local address, which brings the problem of inconsistent URL behavior.

When you take the current Context.Request.URL, you will find that the system automatically ignores the. symbol in the address, which brings us inconsistent with the URL encoding;

2:target Machine actively refused it (active rejection of target address)

Filddler option's enable IPV6 cancellation.

3: Modify custom rules bring the URL behavior inconsistency

Solve 1 problem, must adopt custom Rules, relevant information: Http://fiddler2.com/documentation/KnowledgeBase/FiddlerScript/ModifyRequestOrResponse

For two virtual sites in my solution, change the policy for fiddler 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 is not to get the AAA this URL, but localhost., which is still the problem of inconsistent URL behavior

4: Set the site to "use local IIS Web server"

The site where debugging is set in VS is not development server, but IIS, where the URL is filled out as a local IP address, such as: HTTP://192.168.80.1/. Well, all of this, or can only blame IE on the local address does not go agent. Because we know fiddler opened, the actual is for IE set to go its own agent.