Jeff White wrote:
From: "Vanga"Come to think of it, probably I should take your cue and run the browser in debug/trace mode and dump all the info. and see what is happening between browser and web server. I do not know how I can do this with Internet Explorer.A _must_ read for _all_ OS web server admins (since Microsoft's Windows Shell browser, Internet Explorer, is the most used on the Internet)!A "how to" use Microsoft's free Fiddler debugger (in Internet Explorer) to see Internet and Internet Explorer HTTP actions.<quote> Snip I fired up my trusty HTTP debugger, Microsoft Fiddler. Some developers in the audience might be scratching their heads-- I've got the full source for IE on my computer, so why start by looking at the traffic? Simple-it's usually the clearest way to see what's really going on. HTTP is beautiful that way- if you can see both the traffic of a working scenario and the traffic from a broken scenario, you can resolve most problems of this nature. </quote> A HTTP Detective Story by Eric Lawrence http://blogs.msdn.com/ie/archive/2005/03/12/394526.aspx Jeff
I just installed Fiddler and looks great. I will post the results tomorrow. Thanks Vanga --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|