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?
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?
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?)
TOS breakers will be suspended regardless of race, creed, national origin, hair color, or favorite food. Thanks for your understanding!
Anything in your localhost wont be using any Bandwidth.Because as the word says every thing is locally accessible.
But think about the case that you are having an embedded video in your webpage (say youtube video).In this case it will use your Bandwidth.
As Agenator said if you have any doubt just unplug your internet Cable and look whats happening.
it doesn't leave your network so it doesn't use bandwidth. if you have content on that page that isn't on your server (images, flash videos, etc...), then that will, but a basic html page or one with content on the local server will not use bandwidth.
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.
My signature likes cookies! Do you? :D
Definitely not. Any URL that is pointed to 127.0.0.1 in your hosts file will also not pass through your modem.
If you are unsure about ip then simply run a tracert test
If you see many lines like on the second example then it's probably using your internet connection.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>
Oh I didn't even think of that :laugh:
Now I can reload 700 times to check something without feeling guilty.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.
Thanks to everyone for not making me feel like a moron for asking a noobish question like this.