Blocking Methods

.htaccess syntax

[keyplyr]

I wish to ban a website from pulling my files.

Is there a difference between these two methods? Any preference of the two? Thanks.

SetEnvIf Remote_Host ^###\.##\.###\.##$ ban
<Files *>
Order Deny,Allow
Deny from env=ban
</Files>

RewriteCond %{REMOTE_HOST} ^###\.##\.###\.##$
RewriteRule .* - [F]

[jdMorgan]

You don't actually have to use the SetEnvIf method if you just want to block IP addresses. For example,

<Files *>
Order Deny,Allow
Deny from ^###\.##\.###\.##$

will also work. SetEnvIf is only needed when you wish to Deny based on server variables other than IP address or remote hostname.

As to which is "better," that's largely a matter of preference or necessity; Some servers don't support mod_rewrite, so the only way to block access is with mod_access (or a script). Other subtle differences may also be important in the decision too; In some server configurations, mod_access-denied accesses are logged to the server error log, while mod_rewrite-denied accesses are logged to the server access log.

Jim

[Bernie]

is there also a way to block entire ip-ranges?

thank you.

[jdMorgan]

Yes, you can omit trailing octets from the address to be matched, or you can use network/netmask or network/CIDR notation to block ranges.

For example, you could use
Deny from 123.45.67.
to block addresses in the range 123.45.67.0 through 123.45.67.255

Or you could use
Deny from 123.45.67.0/255.255.255.0
Or
Deny from 123.45.67.0/24

See mod_access [httpd.apache.org] and mod_setenvif [httpd.apache.org] for more details.

Jim

[Bernie]

great thanks, i tried with the * but that was obviously wrong.
:-)

[Bernie]

oh by the way, wouldn't this also work:

Deny from 202.104.0.0 - 202.104.255.255

[kevinpate]

you can accomplish your goal, with a somewhat smaller file size, if you simplify it to:

Deny from 202.104.