Server To Server Tracking

[Kevin]

There needs to be better instructions on how to set up tracing of calls from a web server to other services.  I've looked through all the documentation it makes it appear that this is as simple as setting the defaultProxy and viola, you'll get the server-to-server traffic to you so desperately need to see.  Except that it doesn't work.

What has to be done is change the IIS App Pool so that the application runs in the same account as your using to run fiddler.  Then all of the other things that need to happen still need to be changed (adding the Fiddler certificate, defaultProxy, etc.).

[Nick Iliev]

Hello Kevin,

 

Thank you for your feedback about the need to extend further the Fiddler documentation!

As far as I understood you have a scenario where you need to capture all incoming & outgoing traffic from/to an IIS server. If that is the case, you could check this forum thread for instructions on how to achieve that.

If, however, you are only need to capture traffic from .NET application that uses IIS then you could use the web.config file to set the Fiddler proxy:

<system.net>
  <defaultProxy>
    <proxy  proxyaddress="http://127.0.0.1:8888" />      
  </defaultProxy>
</system.net>

 

Regards,
Nick Iliev
Progress Telerik