I dont know much about this, but I suppose an easy test to see if it does is to unplug your internet cable from the back of your computer and see if you can still access localhost. Chances are that you will be able to since its hosted on your computer, but again I'm no expert... But in the long run, you really aren't eating up that much bandwidth by accessing localhost (or are you?)
Thanks everybody! I did notice when the modem was turned off I could still access localhost but I wanted to double check that it wasn't going through the modem when it was on.
I have apache on my computer to test websites. When I access something through localhost, does it use up bandwidth from the ISP, or does it not even go through my ISP at all?
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\dima>tracert 127.0.0.1
Tracing route to localhost [127.0.0.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms localhost [127.0.0.1]
Trace complete.
C:\Documents and Settings\dima>tracert google.ca
Tracing route to google.ca [72.14.207.104]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 45 ms 43 ms 44 ms lo-100.erx05.tor.packetflow.ca [206.248.154.105]
3 42 ms 43 ms 43 ms 2120.ae0.bdr02.tor.packetflow.ca [69.196.136.66]
4 44 ms 43 ms 43 ms gw-google.torontointernetxchange.net [198.32.245
.6]
5 44 ms 43 ms 43 ms 216.239.47.112
6 58 ms 44 ms 43 ms 72.14.236.183
7 54 ms 45 ms 44 ms 72.14.236.134
8 46 ms 44 ms 43 ms eh-in-f104.google.com [72.14.207.104]
Trace complete.
C:\Documents and Settings\dima>
If you are unsure about ip then simply run a tracert test
Now I can reload 700 times to check something without feeling guilty. :biggrin:C:\>tracert 127.0.0.1
Tracing route to localhost [127.0.0.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms localhost [127.0.0.1]
Trace complete.