8

situation:

my website (which contains the WCF service) is hosted in IISExpres port number 58366 (http://localhost:58366/myapp)

I have a winforms client which connects to the wcf service using BasicHttpBinding

I want to debug my wcf calls using fiddler, but can't seem find how to redirect wcf calls through fiddler.

rekna
  • 5,313
  • 7
  • 45
  • 54

2 Answers2

6

IISExpress idiotically binds to the hostname "localhost", not just to the port, so conventional workarounds as with adding a dot to the hostname don't work. Solution seems to be here. Note the last part of the selected answer: Use "localhost.fiddler" and Fiddler will emit "localhost" when proxying.

Community
  • 1
  • 1
Jon Davis
  • 6,562
  • 5
  • 43
  • 60
2

Rick Strahl has a good article on this here: http://www.west-wind.com/weblog/posts/2009/Jan/14/Monitoring-HTTP-Output-with-Fiddler-in-NET-HTTP-Clients-and-WCF-Proxies

Pretty sure a winforms app will usually pick up the default system proxy as set by fiddler. Are you operating on localhost? Try connecting to your machine name.

russau
  • 8,928
  • 6
  • 39
  • 49
  • IIS express shouldn't be a factor, as you want to configure the winforms app to talk via fiddler. – russau May 25 '11 at 00:15
  • IIS Express binds to the "localhost" hostname, not just the loopback adapter at 127.0.0.1. It is a misconfiguration out of the box. The Visual Studio Web Development Server (Cassini) as well as IIS both handle your scenario fine; but not IIS Express. – Jon Davis Oct 19 '12 at 20:20