Blocking ip's...

[Oddysey]

geriatric;

Quote:I am surprised I can still read english 

Who says you are reading English? :o I'm typing this in Lower Elbonian! <_< [lol]

Seriously, you're welcome. I've kept it brief, partially because we've already hashed this out in other threads on this forum. Feel free to search for 'em, they aren't too old, so their still relevant. :P

Quote:Host files I have seen have been as you say, only usually 127.0.0.1 hehe. You are saying normally they do not have www. only name.com? So my end product would be, under #User added section#

badplace.com
and not
http://www.badplace.com

You almost have the right of it. To emulate Paul Harvey - And now......... for the rest of the story. (copyright 1974-2004, Paul Harvey Enterprises, Inc.)

There is no law requiring a website to use the www. prefix. In point of fact, many sites across the 'net will respond correctly to either form of their address, with or without the prefix. Not all, but many. This is precisely why your HOSTS file must include all the possible permutations - it's being passed a string of text, and it has to look for an exact match, no exceptions allowed. (Well, actually, the HOSTS file is being examined by a sub-routine deep down in the bowels of the OS, a routine which isn't very smart, if you ask me. This has been virtually unmodified, nor updated, since JC was a Corporal. IMHO, by now it should at least handle regexp's. [angry])

So, we use 127.0.0.1 to return a numeric address for the string of text representing the badguy site, and of course our localhost located at 127.0.0.1 has nada sitting in its little teacup, perforce we see nada on our screens. Once again, through the miracle of modern electronics, we've been saved from being forced to visit a badguy site. Ain't life wunnerful? [rolleyes]

Quote:I have seen an online tutorial that says this

Quote:5. Restrictions on the hosts file don't apply to the Prox URL Kill feature. Wildcards allow it to block ads without blocking an entire site and it can be used with IP numbers. Examples:

http://207.218.316.23/pic.jpg or http://www.someplace.com/xyz/pic.jpg

Absolutely correct. Proxo is merely passing the address, as a string of text, out to the 'net, hence, it's fine with such a scheme as shown above. What it really means is that the HOSTS file was <span style='color:red'><span style='font-size:10pt;line-height:100%'>not</span></span> consulted, as a numeric address was already in place. This means that a badguy site can be visited - your HOSTS file protection was rendered null and void (pwned, in l33t-speak). Best to use Proxo to filter for this kind of behavior.

OK, gotta go. Keep those cards and letters comin', folks! [smoke]


Oddysey