views:

2818

answers:

3

I am looking for some way to elegantly inspect XmlHttpRequests in IE8. I wouldn't mind a plugin or an external program. I have yet to find anything that works nearly as well as Firebug.

I have already tried Julien Couvreur's bookmark debugger, but it did not seem to work with Prototype. Julien's Script

+1  A: 

Firebug Lite has some XHR support. I am still a bit hazy on how to use it though; I think you give it a javascript variable reference that resolves to a XHR object and Firebug will then follow that element.

You can of course also sprinkle firebug console messages throughout your code to try and follow what is going on with IE XHR calls.

Martijn Pieters
+7  A: 

Fiddler is the main tool for Request Response Debuggin in IE... ( FireBug in FireFox )

http://www.fiddler2.com/fiddler2/

BigBlondeViking
I have used Fiddler before and completely forgot about it. For those browsing this question it snag's IE's network connection and acts like a local proxy routing all IE traffic through it. This is probably as close to Firebug's offerings as one can get.
Raegx
The mixture of IE Developer Tools (F12 in IE8 ) and fiddler you get far more support than in the old IE 6 days... Still wishing for built-in DOM viewer like FireBug... ( makes writing JS far more easy )
BigBlondeViking
This answer just saved me hours of tedious debugging. Fiddler showed me that in one case my server wasn't sending HTTP headers with its XML response. FF and Safari didn't care, but IE7, IE8 and Chrome barfed with no clue what was going on. Thanks Stackoverflow!!!
Berry
Check out firebug Lite
Gutzofter
A: 

Fiddler is an alright option, but I do wish they would add direct support in develipers tools ( f12 ) in IE 8.

Fiddler does not work over VPN connections so I have some issues using it. It's a proxy solution which can lead to other issues with headers and such.

I don't see why IE 8 can't directly report them like Chrome's built in tools and Firebug in Firefox.

Fiddler is really good for debugging weird broken .js downloads and such though. I actually use it with Chrome and Firefox to detect differences between the three browsers. Many JS libraries run code only for IE to get around the quirks.

twiggy