Capturing [SOAP] packets on localhost

449 views
Skip to first unread message

robertg...@btclick.com

unread,
Apr 17, 2009, 11:22:29 AM4/17/09
to Fiddler
I'm trying to capture SOAP packets between a WCF client and server
application running on the same machine. I'm using WsHttp as the
binding and I've tried setting the localhost to both ipv4.fiddler and
127.0.0.1.

The server is running in debug mode in VS 2008 and is listening on
port 8867.

Fiddler isn't tracing anything. Any clues about what I need to do?

EricLaw

unread,
Apr 17, 2009, 5:56:30 PM4/17/09
to Fiddler
I'm not sure I understand what "I've tried setting the localhost to
both ipv4.fiddler and 127.0.0.1." means?

Do you see non-local requests going through Fiddler? If not, you'll
need to set your machine.config to point to the proxy; see
www.fiddler2.com/fiddler/help/hookup.asp

On Apr 17, 8:22 am, "robertgtayl...@btclick.com"

robertg...@btclick.com

unread,
Apr 18, 2009, 8:29:29 AM4/18/09
to Fiddler
I changed the address in the WCF config of the client app from
'localhost:8867' to 'ipv4.fiddler:8867' and '127.0.0.1:8867'.

The 'SOAP Service' is a console app listening on port 8867 (wsHttp).
The client app is a WinForms app that uses WCF.

Fiddler shows me http packets that are to external connections. I also
have a REST-based demonstration that I created in the same way (WCF,
Console app) and I can see the packets here if I use the browser (as a
client) and the URL "http://ipv4.fiddler:8000/Phonebook". I haven't
got a client app for the REST service, yet.

EricLaw

unread,
Apr 18, 2009, 11:55:28 AM4/18/09
to Fiddler
Neither localhost nor 127.0.0.1 is likely to work because .NET is
hardcoded to bypass proxies for localhost.

Do you see non-local requests *from your Winforms app* going through
Fiddler? If not, you'll need to set your machine.config to point to
the proxy; see www.fiddler2.com/fiddler/help/hookup.asp

On Apr 18, 5:29 am, "robertgtayl...@btclick.com"

vplusplus

unread,
Apr 25, 2009, 2:24:36 PM4/25/09
to Fiddler

Try this... Should work...

Add the following entry to your hosts file:
127.0.0.1 mymachine

If you are using Vista or W7, make sure you start notepad as
administrator before editing the file, or else you wont be able to
save the file.

Try http://mymachine:yourport/yourpath/yourresource

Other suggested workaround (using http://ipv4.fiddler:port/resource or
http://ipv6.fiddler:port/resource) will work.
But, if you are not running fiddler, the uri will fail.

The host entry work-around should work irrespective of if the fiddler
is running or not.

There is nothing special about the host name 'mymachine'.
You can use any host name (just dont use localhost).



Reply all
Reply to author
Forward
0 new messages