Comments on: Localhost HTTP debugging with Fiddler http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/ while(!(succeed = try())); Tue, 07 Oct 2008 17:01:53 +0000 http://wordpress.org/?v=2.6.2 By: EricLaw [MSFT] http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-8498 EricLaw [MSFT] Thu, 26 Jun 2008 01:50:57 +0000 http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-8498 Other workarounds are here: http://www.fiddler2.com/fiddler/help/hookup.asp#Q-LocalTraffic Other workarounds are here: http://www.fiddler2.com/fiddler/help/hookup.asp#Q-LocalTraffic

]]> By: Michael Conly http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-2223 Michael Conly Wed, 26 Mar 2008 22:24:53 +0000 http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-2223 <strong>Localhost HTTP debugging with Fiddler - repost</strong> Debugging with http traffic with Fiddler works great, until you try to intercept traffic on localhost. Localhost HTTP debugging with Fiddler - repost

Debugging with http traffic with Fiddler works great, until you try to intercept traffic on localhost.

]]> By: Nordes http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-2204 Nordes Wed, 26 Mar 2008 12:33:35 +0000 http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-2204 As Nick Berardi Says: “localhost.” (the dot at the end is important) It works #1 even with port number "http://localhost.:2128/" As Nick Berardi Says:
“localhost.” (the dot at the end is important)

It works #1 even with port number “http://localhost.:2128/”

]]> By: Nick Berardi http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-1773 Nick Berardi Wed, 12 Mar 2008 13:03:08 +0000 http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-1773 Jeffro, As stated above when working on teams, you need something that is common in your project configurations. Unfortunately the computer name is... well unique to the computer. Jeffro,

As stated above when working on teams, you need something that is common in your project configurations. Unfortunately the computer name is… well unique to the computer.

]]> By: Nick Berardi http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-1766 Nick Berardi Wed, 12 Mar 2008 01:06:46 +0000 http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-1766 Don't know how long it will be around, but basically it is just a DNS lookup there is no actual site for it. So stability is not an issue. Created: 2003-07-02 Updated: 2007-06-17 Expires: 2008-07-02 Registrant SOMESITE.COM c/o Whois IDentity Shield 142-757 W. Hastings St., Suite #777 Vancouver, BC Canada V6C 1A1 Administrative Contact SOMESITE.COM c/o Whois IDentity Shield 142-757 W. Hastings St., Suite #777 Vancouver, BC Canada V6C 1A1 E-mail: KbYDlJHYrd5MNdcCS/ Technical Contact SOMESITE.COM c/o Whois IDentity Shield 142-757 W. Hastings St., Suite #777 Vancouver, BC Canada V6C 1A1 E-mail: tInMTdMS88zN3zlv6vN8QAR1e/ZcjWr+jRymBAqH8MsEOT4fJTU=@2008.identityshield.com Name servers for this domain: NS1.HITFARM.COM 72.51.27.54 NS2.HITFARM.COM 217.68.70.72 NS3.HITFARM.COM 64.40.116.38 Don’t know how long it will be around, but basically it is just a DNS lookup there is no actual site for it. So stability is not an issue.

Created: 2003-07-02
Updated: 2007-06-17
Expires: 2008-07-02

Registrant
SOMESITE.COM
c/o Whois IDentity Shield
142-757 W. Hastings St., Suite #777
Vancouver, BC
Canada V6C 1A1

Administrative Contact
SOMESITE.COM
c/o Whois IDentity Shield
142-757 W. Hastings St., Suite #777
Vancouver, BC
Canada V6C 1A1
E-mail: KbYDlJHYrd5MNdcCS/

Technical Contact
SOMESITE.COM
c/o Whois IDentity Shield
142-757 W. Hastings St., Suite #777
Vancouver, BC
Canada V6C 1A1
E-mail: tInMTdMS88zN3zlv6vN8QAR1e/ZcjWr+jRymBAqH8MsEOT4fJTU=@2008.identityshield.com

Name servers for this domain:

NS1.HITFARM.COM 72.51.27.54
NS2.HITFARM.COM 217.68.70.72
NS3.HITFARM.COM 64.40.116.38

]]> By: Mark Brackett http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-1764 Mark Brackett Tue, 11 Mar 2008 23:48:55 +0000 http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-1764 I don't know how reliable it is - AFAIK, only example.* is reserved for examples, but it's an interesting trick. I wonder who owns somesite.com and why they pointed it to 127.0.0.1..... I don’t know how reliable it is - AFAIK, only example.* is reserved for examples, but it’s an interesting trick. I wonder who owns somesite.com and why they pointed it to 127.0.0.1…..

]]> By: Jeffro http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-1756 Jeffro Tue, 11 Mar 2008 19:54:38 +0000 http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-1756 See any reason to not use your netbios name? eg: http://mycomputername/mysite See any reason to not use your netbios name? eg: http://mycomputername/mysite

]]> By: Nick Berardi http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-1751 Nick Berardi Tue, 11 Mar 2008 14:46:53 +0000 http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-1751 "localhost." has the nasty habit of not working with port numbers at least in my experience. “localhost.” has the nasty habit of not working with port numbers at least in my experience.

]]> By: Alun Harford http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-1750 Alun Harford Tue, 11 Mar 2008 14:45:10 +0000 http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-1750 You can also use "localhost." You can also use “localhost.”

]]> By: Nick Berardi http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-1748 Nick Berardi Tue, 11 Mar 2008 13:56:01 +0000 http://www.coderjournal.com/2008/03/localhost-http-debugging-with-fiddler/#comment-1748 I understand and know about the hosts and lmhosts file in c:\windows\system32\drivers\etc. And I know about the using your local machine trick too. Also by using your hosts file that is what causes the issue, because the hosts file bypasses the process of sending the request through the normal route, when mapped to 127.0.0.1, which is why localhost doesn't work. If you removed localhost from the hosts and added localhost to an external DNS you would see localhost to start working in Fiddler. However my problem is when dealing with a team of developers the easiest solution is usually the best solution. And it is almost impossible to edit your hosts file in Windows Vista because of the protections placed on it, and as outlined above it wouldn't work anyways. So working on a team where everybody has Vista and different machine names I choose to use www.somesite.com. I probably should have spelled it out, but those are my reasons for choosing something universal such as www.somesite.com. I understand and know about the hosts and lmhosts file in c:\windows\system32\drivers\etc. And I know about the using your local machine trick too. Also by using your hosts file that is what causes the issue, because the hosts file bypasses the process of sending the request through the normal route, when mapped to 127.0.0.1, which is why localhost doesn’t work. If you removed localhost from the hosts and added localhost to an external DNS you would see localhost to start working in Fiddler.

However my problem is when dealing with a team of developers the easiest solution is usually the best solution. And it is almost impossible to edit your hosts file in Windows Vista because of the protections placed on it, and as outlined above it wouldn’t work anyways. So working on a team where everybody has Vista and different machine names I choose to use http://www.somesite.com.

I probably should have spelled it out, but those are my reasons for choosing something universal such as http://www.somesite.com.

]]>