htaccess "order" Deny, Allow, Deny
Not answering OPs question directly, but for the people finding this question in search of clarity on what's the difference between allow,deny
and deny,allow
:
Read the comma as a "but".
allow but deny
: whitelist with exceptions.
everything is denied, except items on the allow list, except items on the deny listdeny but allow
: blacklist with exceptions.
everything is allowed, except items on the deny list, except items on the allow list
allow only one country access, but exclude proxies within this country
OP needed a whitelist with exceptions, therefore allow,deny
instead of deny,allow
Update : for the new apache 2.4 jump directly to the end.
The Order keyword and its relation with Deny
and Allow
Directives is a real nightmare. It would be quite interesting to understand how we ended up with such solution, a non-intuitive one to say the least.
- The first important point is that the
Order
keyword will have a big impact on howAllow
andDeny
directives are used. - Secondly,
Deny
andAllow
directives are not applied in the order they are written, they must be seen as two distinct blocks (one the forDeny
directives, one forAllow
). - Thirdly, they are drastically not like firewall rules: all rules are applied, the process is not stopping at the first match.
You have two main modes:
The Order-Deny-Allow-mode, or Allow-anyone-except-this-list-or-maybe-not
Order Deny,Allow
- This is an allow by default mode. You optionally specify
Deny
rules. - Firstly, the
Deny
rules reject some requests. - If someone gets rejected you can get them back with an
Allow
.
I would rephrase it as:
Rule Deny
list of Deny rules
Except
list of Allow rules
Policy Allow (when no rule fired)
The Order-Allow-Deny-mode, or Reject-everyone-except-this-list-or-maybe-not
Order Allow,Deny
- This is a deny by default mode. So you usually specify
Allow
rules. - Firstly, someone's request must match at least one
Allow
rule. - If someone matched an
Allow
, you can still reject them with aDeny
.
In the simplified form:
Rule Allow
list of Allow rules
Except
list of Deny rules
Policy Deny (when no rule fired)
Back to your case
You need to allow a list of networks which are the country networks. And in this country you want to exclude some proxies' IP addresses.
You have taken the allow-anyone-except-this-list-or-maybe-not mode, so by default anyone can access your server, except proxies' IPs listed in the Deny
list, but if they get rejected you still allow the country networks. That's too broad. Not good.
By inverting to order allow,deny
you will be in the reject-everyone-except-this-list-or-maybe-not mode.
So you will reject access to everyone but allow the country networks and then you will reject the proxies. And of course you must remove the Deny from all
as stated by @Gerben and @Michael Slade (this answer only explains what they wrote).
The Deny from all
is usually seen with order deny,allow
to remove the allow by default access and make a simple, readable configuration. For example, specify a list of allowed IPs after that. You don't need that rule and your question is a perfect case of a 3-way access mode (default policy, exceptions, exceptions to exceptions).
But the guys who designed these settings are certainly insane.
All this is deprecated with Apache 2.4
The whole authorization scheme has been refactored in Apache 2.4 with RequireAll, RequireAny and RequireNone directives. See for example this complex logic example.
So the old strange Order
logic becomes a relic, and to quote the new documentation:
Controling how and in what order authorization will be applied has been a bit of a mystery in the past
Change your code to
<Limit GET POST>
deny from all
allow from 139.82.0.0/16
allow from 143.54.0.0/16
allow from 186.192.0.0/11
allow from 186.224.0.0/11
</Limit>
This way your htaccess will deny every except those that you explicitly allow with allow from..
A proxy within the allow range can easily be overwritten with an additional deny from..
rule.
Just use order allow,deny
instead and remove the deny from all
line.