| 4:58 am on Jan 8, 2001 (gmt 0)|
Gee, BoneHeadicus...that's a fine question.
Perhaps one of the fine professional webmaster types will join in and answer this plaguing situation you have.
Hang in there...help is on the way.
| 5:02 am on Jan 8, 2001 (gmt 0)|
Bless you my son.
I am overwhelmed by your concern and understanding in the futility of my seemingly endless plight with these h4x0r aggressors.
Oooh whoa is me.
| 9:15 am on Jan 8, 2001 (gmt 0)|
Gee, looks like this one slipped by. Take a look at
| 5:10 pm on Jan 8, 2001 (gmt 0)|
Can I do it by range as Air suggests in the .ht file?
| 5:49 pm on Jan 20, 2001 (gmt 0)|
>>where xxx.xxx.xxx.xxx is a full or partial IP address.
Can I do this by range?
Does anyone know if I can do this by a range?
| 7:14 pm on Jan 20, 2001 (gmt 0)|
ranges are not supported but partial ip addresses are, i.e. 111.222.333. would block everything coming from 111.222.333.???
| 12:11 am on Jan 23, 2001 (gmt 0)|
I'd like to know if it would block a range as well.
I do know that the octet, 333, is non-existent in an IP address.
It think it will not go above either 254 or 255?
I believe I have only seen IPs range:
Wait until the (IPv6 ) 6 octet string IP addresses are rolled out, or are they already?
| 3:59 am on Jan 23, 2001 (gmt 0)|
>I do know that the octet, 333, is non-existent in an IP address.
Yes you are right, it was just an example ... :)
| 11:00 am on Jan 23, 2001 (gmt 0)|
Back to the original q. Not much to it really. If your server is setup to resolve domain names, you can even mix and match:
deny from 211.201.01.14 funstuff.ca 126.96.36.199
Just use a space between thye ip's/names.