mod_access- Apache HTTP Server

From 8937a8aa1090ca98c461edb25c9b5ba68dd4d176 Mon Sep 17 00:00:00 2001 From: Yoshiki Hayashi Date: Mon, 29 Jul 2002 13:53:49 +0000 Subject: [PATCH] Mark Order as directive. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96227 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_access.html.en | 68 ++++++++++++++++++++---------- docs/manual/mod/mod_access.xml | 4 +- 2 files changed, 47 insertions(+), 25 deletions(-) diff --git a/docs/manual/mod/mod_access.html.en b/docs/manual/mod/mod_access.html.en index 154d058334..23af4cc539 100644 --- a/docs/manual/mod/mod_access.html.en +++ b/docs/manual/mod/mod_access.html.en @@ -1,10 +1,13 @@ -mod_access- Apache HTTP Server

Apache HTTP Server Version 2.0
Apache Module mod_access
Description: Provides access control based on client hostname, IP -address, or other characteristics of the client request.
Status: Base
Module Identifier: access_module
Summary
-
The directives provided by mod_access are used in <Directory>, <Files>, and <Location> sections as well as +mod_access - Apache HTTP Server
Apache HTTP Server Version 2.0
Apache Module mod_access
Description: + Provides access control based on client hostname, IP +address, or other characteristics of the client request.
Status: + Base
Module Identifier: + access_module
Summary
+
The directives provided by mod_access are used in <Directory>, <Files>, and <Location> sections as well as .htaccess files to control access to particular parts of the server. Access can be controlled based on the client hostname, IP address, or @@ -17,7 +20,7 @@ address, or other characteristics of the client request.Both host-based access restrictions and password-based authentication may be implemented simultaneously. In that case, - the Satisfy directive is used + the Satisfy directive is used to determine how the two sets of restrictions interact.

In general, access restriction directives apply to all @@ -25,11 +28,17 @@ address, or other characteristics of the client request.POST, etc). This is the desired behavior in most cases. However, it is possible to restrict some methods, while leaving other methods unrestricted, by enclosing the directives - in a <Limit> section.
-
Directives
Allow
Deny
Order
See also
Satisfy
Require
Allow Directive
Description: Controls which hosts can access an area of the -server
Syntax: Allow from + in a <Limit> section.
+
Directives
Allow
Deny
Order
See also
Satisfy
Require
Allow Directive
Description: + Controls which hosts can access an area of the +server
Syntax: + Allow from all|host|env=env-variable - [host|env=env-variable] ...
Context: directory, .htaccess
Override: Limit
Status: Base
Module: mod_access
+ [host|env=env-variable] ...
Context: + directory, .htaccess
Override: + Limit
Status: + Base
Module: + mod_access

The Allow directive affects which hosts can access an area of the server. Access can be controlled by @@ -55,7 +64,7 @@ serverfoo.apache.org but it will not match fooapache.org. This configuration will cause the server to perform a reverse DNS lookup on the - client IP address, regardless of the setting of the HostnameLookups + client IP address, regardless of the setting of the HostnameLookups directive.
A full IP address
@@ -102,7 +111,7 @@ server mod_setenvif. Therefore, this directive can be + mod_setenvif. Therefore, this directive can be used to allow access based on such factors as the clients User-Agent (browser type), Referer, or other HTTP request header fields.
@@ -120,17 +129,30 @@ SetEnvIf User-Agent ^KnockKnock/2.0 let_me_in

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 Directive
Description: Controls which hosts are denied access to the -server
Syntax: Deny from +
Deny Directive
Description: + Controls which hosts are denied access to the +server
Syntax: + Deny from all|host|env=env-variable - [host|env=env-variable] ...
Context: directory, .htaccess
Override: Limit
Status: Base
Module: mod_access
+ [host|env=env-variable] ...
Context: + directory, .htaccess
Override: + Limit
Status: + Base
Module: + mod_access

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 Directive
Description: Controls the default access state and the order in which +
Order Directive
Description: + Controls the default access state and the order in which Allow and Deny are -evaluated.
Syntax: Order ordering
Default: Order Deny,Allow
Context: directory, .htaccess
Override: Limit
Status: Base
Module: mod_access
+evaluated.
Syntax: + Order ordering
Default: + Order Deny,Allow
Context: + directory, .htaccess
Override: + Limit
Status: + Base
Module: + mod_access

The Order directive controls the default access state and the order in which Allow and Deny directives are evaluated. @@ -187,7 +209,7 @@ evaluated.
-
On the other hand, if the Order in the last +
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, @@ -197,7 +219,7 @@ evaluated.allow.
-
The presence of an Order directive can affect +
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,
@@ -216,9 +238,9 @@ evaluated.Allow or Deny directive occurring in a - <Location> section will + <Location> section will always be evaluated after an Allow or Deny directive occurring in a - <Directory> section or + <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 diff --git a/docs/manual/mod/mod_access.xml b/docs/manual/mod/mod_access.xml index d9aa95bbe5..0607d181da 100644 --- a/docs/manual/mod/mod_access.xml +++ b/docs/manual/mod/mod_access.xml @@ -260,7 +260,7 @@ evaluated. Deny from foo.apache.org
-
On the other hand, if the Order in the last +
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, @@ -270,7 +270,7 @@ evaluated. be allowed access because the default state will change to allow.
-
The presence of an Order directive can affect +
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 -- 2.40.0