Removing controls in subdirectories

-switch (ap_satisfies(r)) { -case SATISFY_ALL: -case SATISFY_NOSPEC: - if ((access_status = ap_run_access_checker(r)) != 0) { - return decl_die(access_status, "check access", r); - } - - if (ap_some_auth_required(r)) { - if (((access_status = ap_run_check_user_id(r)) != 0) - || !ap_auth_type(r)) { - return decl_die(access_status, ap_auth_type(r) - ? "check user. No user file?" - : "perform authentication. AuthType not set!", - r); - } - - if (((access_status = ap_run_auth_checker(r)) != 0) - || !ap_auth_type(r)) { - return decl_die(access_status, ap_auth_type(r) - ? "check access. No groups file?" - : "perform authentication. AuthType not set!", - r); - } - } - break; - -case SATISFY_ANY: - if (((access_status = ap_run_access_checker(r)) != 0)) { - if (!ap_some_auth_required(r)) { + if ((access_status = ap_run_access_checker(r)) != 0) { return decl_die(access_status, "check access", r); } - if (((access_status = ap_run_check_user_id(r)) != 0) - || !ap_auth_type(r)) { - return decl_die(access_status, ap_auth_type(r) - ? "check user. No user file?" - : "perform authentication. AuthType not set!", - r); + if ((access_status = ap_run_check_user_id(r)) != 0) { + return decl_die(access_status, "check user", r); } - if (((access_status = ap_run_auth_checker(r)) != 0) - || !ap_auth_type(r)) { - return decl_die(access_status, ap_auth_type(r) - ? "check access. No groups file?" - : "perform authentication. AuthType not set!", - r); + if ((access_status = ap_run_auth_checker(r)) != 0) { + return decl_die(access_status, "check authorization", r); } - } - break; -}

The require Directives + +

Apache's Require and + Reject directives are + used during the authorization phase to ensure that a user is allowed or + denied access to a resource. mod_authz_host extends the + authorization types with env, ip, + host and all. Other authorization types may also be + used but may require that additional authorization modules be loaded.

+ +

These authorization providers affect which hosts can access an area of the server. Access can be controlled by hostname, IP Address, IP Address range, or by other characteristics of the client request captured in environment variables.

The first argument to this directive is always - from. The subsequent arguments can take three - different forms. If Allow from all is specified, then - all hosts are allowed access, subject to the configuration of the - Deny and Order directives as discussed - below. To allow only particular hosts or groups of hosts to access - the server, the host can be specified in any of the - following formats:

- -

A (partial) domain-name: - Example: - Allow from apache.org
- Allow from .net example.edu - -
Hosts whose names match, or end in, this string are allowed - access. Only complete components are matched, so the above - example will match foo.apache.org but it will not - match fooapache.org. This configuration will cause - Apache to perform a double reverse DNS lookup on the client IP - address, regardless of the setting of the HostnameLookups directive. It will do - a reverse DNS lookup on the IP address to find the associated - hostname, and then do a forward lookup on the hostname to assure - that it matches the original IP address. Only if the forward - and reverse DNS are consistent and the hostname matches will - access be allowed.
A full IP address: - Example: - Allow from 10.1.2.3
- Allow from 192.168.1.104 192.168.1.205 - -
An IP address of a host allowed access
A partial IP address: - Example: - Allow from 10.1
- Allow from 10 172.20 192.168.2 - -
The first 1 to 3 bytes of an IP address, for subnet - restriction.
A network/netmask pair: - Example: - Allow from 10.1.0.0/255.255.0.0 - -
A network a.b.c.d, and a netmask w.x.y.z. For more - fine-grained subnet restriction.
A network/nnn CIDR specification: - Example: - Allow from 10.1.0.0/16 - -
Similar to the previous case, except the netmask consists of - nnn high-order 1 bits.

- -

Note that the last three examples above match exactly the - same set of hosts.

require env -

IPv6 addresses and IPv6 subnets can be specified as shown - below:

- - - Allow from 2001:db8::a00:20ff:fea7:ccea
- Allow from 2001:db8::a00:20ff:fea7:ccea/10 - - -

The third format of the arguments to the - Allow directive allows access to the server +

The env provider allows access to the server to be controlled based on the existence of an environment variable. When Allow from - env=env-variable is specified, then the request is + href="../env.html">environment variable. When Require + env env-variable is specified, then the request is allowed access if the environment variable env-variable exists. The server provides the ability to set environment variables in a flexible way based on characteristics of the client @@ -175,162 +87,126 @@ server used to allow access based on such factors as the clients User-Agent (browser type), Referer, or other HTTP request header fields.

- + Example: SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in
<Directory /docroot>
- Order Deny,Allow
- Deny from all
- Allow from env=let_me_in
+ Require env let_me_in
</Directory> - +

In this case, browsers with a user-agent string beginning with KnockKnock/2.0 will be allowed access, and all others will be denied.

- - - - -Deny -Controls which hosts are denied access to the -server - Deny from all|host|env=env-variable -[host|env=env-variable] ... -directory.htaccess - -Limit - - -

This directive allows access to the server to be restricted - based on hostname, IP address, or environment variables. The - arguments for the Deny directive are - identical to the arguments for the Allow directive.

- - - - -Order -Controls the default access state and the order in which -Allow and Deny are -evaluated. - Order ordering -Order Deny,Allow -directory.htaccess - -Limit - - -

The Order directive controls the default - access state and the order in which Allow and Deny directives are evaluated. - Ordering is one of

- -

Deny,Allow: The Deny directives - are evaluated before the Allow directives. Access is - allowed by default. Any client which does not match a - Deny directive or does - match an Allow - directive will be allowed access to the server.
Allow,Deny: The Allow - directives are evaluated before the Deny directives. Access is denied - by default. Any client which does not match an Allow directive or does match a - Deny directive will be - denied access to the server.
Mutual-failure: Only those hosts which appear on the Allow list and do not appear on - the Deny list are - granted access. This ordering has the same effect as Order - Allow,Deny and is deprecated in favor of that - configuration.

- -

Keywords may only be separated by a comma; no whitespace is - allowed between them. Note that in all cases every Allow and Deny statement is evaluated.

- -

In the following example, all hosts in the apache.org domain - are allowed access; all other hosts are denied access.

+ +

require ip + +

The ip provider allows access to the server + to be controlled based on the IP address of the remote client. + When Require ip ip-address is specified, + then the request is allowed access if the IP address matches.

+ +

A full IP address:

+ - Order Deny,Allow
- Deny from all
- Allow from apache.org + Require ip 10.1.2.3
+ Require ip 192.168.1.104 192.168.1.205 -

In the next example, all hosts in the apache.org domain are - allowed access, except for the hosts which are in the - foo.apache.org subdomain, who are denied access. All hosts not - in the apache.org domain are denied access because the default - state is to deny access to the server.

An IP address of a host allowed access

+ +

A partial IP address:

+ + + Require ip 10.1
+ Require ip 10 172.20 192.168.2 + +

The first 1 to 3 bytes of an IP address, for subnet + restriction.

+ +

A network/netmask pair:

+ + + Require ip 10.1.0.0/255.255.0.0 + +

A network a.b.c.d, and a netmask w.x.y.z. For more + fine-grained subnet restriction.

+ +

A network/nnn CIDR specification:

+ + + Require ip 10.1.0.0/16 + +

Similar to the previous case, except the netmask consists of + nnn high-order 1 bits.

+ +

Note that the last three examples above match exactly the + same set of hosts.

+ +

IPv6 addresses and IPv6 subnets can be specified as shown + below:

+ + + Require ip 2001:db8::a00:20ff:fea7:ccea
+ Require ip 2001:db8::a00:20ff:fea7:ccea/10 + + + +

require host + +

The host provider allows access to the server + to be controlled based on the host name of the remote client. + When Require host host-name is specified, + then the request is allowed access if the host name matches.

+ +

A (partial) domain-name

+ - Order Allow,Deny
- Allow from apache.org
- Deny from foo.apache.org + Require host apache.org
+ Require host .net example.edu + +

Hosts whose names match, or end in, this string are allowed + access. Only complete components are matched, so the above + example will match foo.apache.org but it will not + match fooapache.org. This configuration will cause + Apache to perform a double reverse DNS lookup on the client IP + address, regardless of the setting of the HostnameLookups directive. It will do + a reverse DNS lookup on the IP address to find the associated + hostname, and then do a forward lookup on the hostname to assure + that it matches the original IP address. Only if the forward + and reverse DNS are consistent and the hostname matches will + access be allowed.

+ +

require all + +

The all provider mimics the functionality the + was previously provided by the 'Allow from all' and 'Deny from all' + directives. This provider can take one of two arguments which are + 'granted' or 'denied'. The following examples will grant or deny + access to all requests.

On the other hand, if the Order in the last - example is changed to Deny,Allow, all hosts will - be allowed access. This happens because, regardless of the - actual ordering of the directives in the configuration file, - the Allow from apache.org will be evaluated last - and will override the Deny from foo.apache.org. - All hosts not in the apache.org domain will also - be allowed access because the default state will change to - allow.

- -

The presence of an Order directive can affect - access to a part of the server even in the absence of accompanying - Allow and Deny directives because of its effect - on the default access state. For example,

+ + Require all granted
+ - <Directory /www>
- - Order Allow,Deny
- - </Directory> + Require all denied
-

will deny all access to the /www directory - because the default access state will be set to - deny.

- -

The Order directive controls the order of access - directive processing only within each phase of the server's - configuration processing. This implies, for example, that an - Allow or Deny directive occurring in a - Location section will - always be evaluated after an Allow or Deny directive occurring in a - Directory section or - .htaccess file, regardless of the setting of the - Order directive. For details on the merging - of configuration sections, see the documentation on How Directory, Location and Files sections - work.

- - +

+ + +