Reputation: 2784
I have a simple windows console app that I have added a service reference to and I am trying to call a method and make a request! I am using the proxy classes generated by .Net when I added the service reference.
The web service is not on my machine but externally hosted by the client!
I am getting an error so I would like to see the HTTP request that is being sent.
I can't see the request on fiddler, why not?
Can I seen the generated request by debugging the console app?
Upvotes: 2
Views: 4979
Reputation: 2115
Aside of Fiddler and embedded tracing tool there is another approach to see generated XML SOAP - custom MessageEncoder. It allows to interceprt original byte content including any malformed xml.
In order to implement tracing using this approach you need to wrap a standard textMessageEncoding with custom message encoder as new binding element and apply that custom binding to endpoint in your config.
Also you can see as example how I did it in my project - wrapping textMessageEncoding, logging encoder, custom binding element and config.
Upvotes: 0
Reputation: 161783
You can see localhost traffic with Fiddler. See this article in the Fiddler FAQ.
You could also turn on WCF Tracing.
Upvotes: 2
Reputation: 3412
Fiddler bypass local traffic. If you want to sniff local address in the client config set .localhost address (with dot prefix).
Upvotes: 0