Fiddler not sniffing SOAP traffic from ASP.NET website

Question

So far I\'ve been successfully using fiddler to sniff web service traffic from both test fixtures, console apps and web projects.

Today I noticed I am not able anymore t

Answer 1

You're probably using a port other than 80 for these http requests. I remember setting up a reverse proxy to look at WCF requests I was making on my local machine during dev. Here's the documentation: http://www.fiddlertool.com/fiddler/help/reverseproxy.asp

Answer 2

What's the client of the web service? ASP.NET?

ASP.NET traffic isn't proxied unless you configure ASP.NET to use a proxy. It's possible/likely that the app.config or machine.config changed such that traffic is no longer getting proxied?

You should have a look at this section: http://www.fiddlerbook.com/fiddler/help/hookup.asp#Q-DOTNET

Answer 3

I ran into this issue a week or so ago. Try this page: http://docs.telerik.com/fiddler/Observe-Traffic/Troubleshooting/NoTrafficToLocalhosthttp://www.fiddler2.com/fiddler/help/hookup.asp#Q-LocalTraffic

The ipv4.fiddler was the part that worked for me. Hope this helps.

Answer 4

If you want to view the http traffic between your web site and your web service on your development machine, and don't want to change your machine.config.

One easy solution is to change the Application Pool Identity of your web site to use your own credentials of the current logged on user. This means that your web site will adopt your proxy settings and will now redirect to Fiddler.

Answer 5

Make sure the web service you are calling (from IE) is not http://localhost/yourwebservice

Fiddler will not intercept localhost traffic from IE, use http://machinename/yourwebservice instead.

Answer 6

Can you try the following -

1. Try stopping the windows firewall and see what happens
2. try using firefox and redirecting traffic to fiddler and see what happens