Msg#: 3505229 posted 1:45 am on Nov 15, 2007 (gmt 0)
I would be wise to block by a combination of remote host, user-agent, and any other factors you can use to narrow down the number of affected users. For example, you might block a half-million potential customers by blocking all shaw customers in Virginia.
If the troublemaker is on a fixed IP address or uses a limited range of IP addresses, it would be far simpler to just block that one address, or a small range of addresses that include his IP address(es).
BTW, the proper term for what you're doing now is "blocking by remote hostname" and the proper syntax [httpd.apache.org] is
Deny from va.shawcable.net
[added] You might also consider feeding him false content -- A page that says it submits, but doesn't really, and then generates a second bogus error message leading him to believe that your site is broken and your business is on its last legs. Never give out any additional true information to your enemies, and make sure that all misinformation is utterly consistent. :) [added]
[edited by: jdMorgan at 1:48 am (utc) on Nov. 15, 2007]
Msg#: 3505229 posted 3:19 am on Nov 15, 2007 (gmt 0)
Is there anyway to block them also by browser? they use netscape browser.
I am very new to this stuff and appreciate any help I can get
There are laws in Canada that would like have more effective (however not immediate)results more stringinent than the US.
I have portions of sub ranges of Shaw denied from both the Maritimes and Alberta. These denies were based actions of a few that were focusing on my pages.
You may reduce the innocents (at least in most instances) by creating a deny which is based on both the IP range and the User Agent, although I'm not so sure that focusing on Netscape would be ideal. Perhaps there is some other phrase or number in the broswer User Agent that would prove more focused?