tags:

views:

1067

answers:

3

I run IIS 5 on my dev machine. I have an asp.net 3.5 web service running on it which I'm calling from a different web app running on the same server. My service is returning an error 500 Internal Server error and I'm troubleshooting it. My request is being sent via a System.Net.HttpWebRequest object and it looks valid from the client's perspective.

I'd like to see the raw incoming HTTP request from the server's perspective. Since the service is being called on loopback, I can't use Wireshark to see it.

IIS Logging shows me the request header but not the post content.

Any suggestions on how I could see the full raw incoming HTTP request in IIS?

Thanks

+3  A: 

I would think you want to add an HTTPModule for logging. Here's a pretty good article on ASP.NET modules and handlers:

That way, when you want to disable logging, you can just remove/comment it from your web.config file.

Dave Nichol
A: 

Your best bet is to run each of your web apps on a different port, and then use something like Fiddler to create a proxy for the port you want to watch. This will monitor all traffic to and from your specific application.

AaronS
+2  A: 

Have you tried using Fiddler? Just use your machine name instead of localhost.

Fiddler works if you're querying from a browser. Webservice calls from within my own apps won't work.
Mr Grieves
@Mr Greieves, it takes a little bit of extra work, but you can manually configure the proxy settings for your webservice calls.
David Kemp