Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Much easier way' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Much easier way
Authored by: Anonymous on Jan 20, '01 12:28:07AM

A much easier way to block web sites that works with Linux and might work with OSX as well is to edit your /etc/hosts file and add lines like the following to it:

0.0.0.0 www.site-to-block.com
0.0.0.0 www.another-site-to-block.com

and so on.

changes to /etc/hosts take effect in subsequently-running applications; already running ones are unaffected, as the file is only read when apps are started.



[ Reply to This | # ]
403 Forbidden error
Authored by: johnnydaboy on Jan 06, '02 12:11:08AM

I tried this and now all I get are 403 Forbidden errors when I try to surf through the proxy server. The Apache log shows the following line:

127.0.0.1 - - [05/Jan/2002:23:14:47 -0500] "GET http://www.nytimes.com/ HTTP/1.0" 403 285

I suppose the 127.0.0.1 localhost is the address of the requesting "machine," in this case, the proxy server. I don't know if that is correct -- the supposition or the setting. The part that I am merely curious about is the HTTP/1.0 part. I thought everything was up to HTTP 1.1. Ideas?

If it's of any consequence, I have DSL and a Linksys router with static addressing.

Can anyone lend me a hand?



[ Reply to This | # ]
Nevermind - 403 Forbidden error
Authored by: johnnydaboy on Jan 07, '02 08:33:24PM

I set up the proxy server on the machine that I work on, just to do it and see if it would work. I set the proxy server to the loopback address but I didn't <Allow> the loopback address in the proxy config file. Duh. Hope this helps anyone else trying this.



[ Reply to This | # ]