I personally hate to open blogs, that just have list of links without more useful information. But as I wrote in Ways to store bookmarks/favorites post, blog is a convinient way to save favorites. So I will just save links for now, and hopefully will add more comments about them later.
FIDDLER supports HTTPS, ensure that "Capture HTTPS Connects" and "Decrypting HTTPS traffic" are ticked in in "Fiddler options". However running Fiddler in "https mode" can have side effects, e.g. my connection to TFs is not working until I close Fiddler .
Web Development Helper by Nikhil Kothari -utility for Web developers and plugs into Internet Explorer.ScottGu (and I agree)prefer it over Fiddler for some ASP.NET and AJAX specific scenarios .
Java application Charles (30 day evaluation) is an HTTP proxy / HTTP monitor / Reverse Proxy that enables a developer to view all of the HTTP traffic between their machine and the Internet.
YATT (Yet Another Trace Tool) - replacement of trace tools ( tcpTrace, proxyTrace, pcapTrace ),
I love Internet Explorer Developer Toolbar , in particular "Find by Click" option.
Using System.Net Tracing - very useful .Net 2.0 features activated in web.config - allows to see details of requests and responces.
Use trace Output tool,e.g.Dbwin32 or DBMonitor.On development machine use Visual Studio Output window.
It is recommended to increase maxdatasize to avoid text truncation,e.g.
<source name="System.Net" maxdatasize="4096">
However if you know more about format of requests and responces, it is better to write custom code to represent data in more readable format.
In paricular, when I am sending SOAP requests, it's better to trace them as XML, rather than view generic hex/ascii dump table (like 6E 64 2E 63 6F 72 70 2E-6D 69 63 72 6F 73 6F 66 : nd.corp.microsof).
It should be considered SOAP extensions, including WSE 3.0.
If you just use Web Services, not WSE 3.0, you can use described in MSDN logging Soap extension, or SoapLogger , or use code from User Friendly ASP.NET Exception Handling.
The hints how to make you class more debugger-friendly (not specific to ASP.NET ) are posted in Easier Debugging with Attributes