httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From n.@apache.org
Subject svn commit: r375322 [1/6] - in /httpd/httpd/trunk/docs/manual: ./ faq/ mod/
Date Mon, 06 Feb 2006 17:56:03 GMT
Author: nd
Date: Mon Feb  6 09:55:59 2006
New Revision: 375322

URL: http://svn.apache.org/viewcvs?rev=375322&view=rev
Log:
fix properties and update transformation

Added:
    httpd/httpd/trunk/docs/manual/mod/mod_access_compat.html   (with props)
    httpd/httpd/trunk/docs/manual/mod/mod_access_compat.html.en   (with props)
Modified:
    httpd/httpd/trunk/docs/manual/bind.html.de
    httpd/httpd/trunk/docs/manual/bind.html.ja.euc-jp
    httpd/httpd/trunk/docs/manual/faq/all_in_one.html.en
    httpd/httpd/trunk/docs/manual/faq/background.html.en
    httpd/httpd/trunk/docs/manual/mod/directives.html.de
    httpd/httpd/trunk/docs/manual/mod/directives.html.es
    httpd/httpd/trunk/docs/manual/mod/directives.html.ja.euc-jp
    httpd/httpd/trunk/docs/manual/mod/directives.html.ko.euc-kr
    httpd/httpd/trunk/docs/manual/mod/index.html.de
    httpd/httpd/trunk/docs/manual/mod/index.html.es
    httpd/httpd/trunk/docs/manual/mod/index.html.ja.euc-jp
    httpd/httpd/trunk/docs/manual/mod/index.html.ko.euc-kr
    httpd/httpd/trunk/docs/manual/mod/mod_access_compat.xml   (contents, props changed)
    httpd/httpd/trunk/docs/manual/mod/mod_dav.html.ja.euc-jp
    httpd/httpd/trunk/docs/manual/mod/mod_dav.html.ko.euc-kr
    httpd/httpd/trunk/docs/manual/mod/mod_rewrite.html.en
    httpd/httpd/trunk/docs/manual/mod/quickreference.html.de
    httpd/httpd/trunk/docs/manual/mod/quickreference.html.es
    httpd/httpd/trunk/docs/manual/mod/quickreference.html.ja.euc-jp
    httpd/httpd/trunk/docs/manual/mod/quickreference.html.ko.euc-kr
    httpd/httpd/trunk/docs/manual/sitemap.html.de
    httpd/httpd/trunk/docs/manual/sitemap.html.es
    httpd/httpd/trunk/docs/manual/sitemap.html.ja.euc-jp
    httpd/httpd/trunk/docs/manual/sitemap.html.ko.euc-kr

Modified: httpd/httpd/trunk/docs/manual/bind.html.de
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/bind.html.de?rev=375322&r1=375321&r2=375322&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/bind.html.de (original)
+++ httpd/httpd/trunk/docs/manual/bind.html.de Mon Feb  6 09:55:59 2006
@@ -24,6 +24,9 @@
 <a href="./ja/bind.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
 <a href="./ko/bind.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a></p>
 </div>
+<div class="outofdate">Diese Übersetzung ist möglicherweise
+            nicht mehr aktuell. Bitte prüfen Sie die englische Version auf
+            die neuesten Änderungen.</div>
 
     <p>Konfiguration der vom Apache verwendeten Adressen und Ports.</p>
   </div>

Modified: httpd/httpd/trunk/docs/manual/bind.html.ja.euc-jp
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/bind.html.ja.euc-jp?rev=375322&r1=375321&r2=375322&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/bind.html.ja.euc-jp [euc-jp] (original)
+++ httpd/httpd/trunk/docs/manual/bind.html.ja.euc-jp [euc-jp] Mon Feb  6 09:55:59 2006
@@ -25,6 +25,8 @@
 <a href="./ja/bind.html" title="Japanese">&nbsp;ja&nbsp;</a> |
 <a href="./ko/bind.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a></p>
 </div>
+<div class="outofdate">This translation may be out of date. Check the
+            English version for recent changes.</div>
 
     <p>Apache が使用するアドレスとポートの設定をします。</p>
   </div>

Modified: httpd/httpd/trunk/docs/manual/faq/all_in_one.html.en
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/faq/all_in_one.html.en?rev=375322&r1=375321&r2=375322&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/faq/all_in_one.html.en (original)
+++ httpd/httpd/trunk/docs/manual/faq/all_in_one.html.en Mon Feb  6 09:55:59 2006
@@ -118,10 +118,10 @@
       Software Foundation, nor make or use modified versions of such
       artwork, except under the following conditions:</p>
       <ul>
-        <li>You may use the <a href="http://httpd.apache.org/docs/apache_pb.gif">'Powered by Apache'
+        <li>You may use the <a href="http://httpd.apache.org/apache_pb.gif">'Powered by Apache'
         graphic</a> on a Web site that is being served by the Apache HTTP
         server software.</li>
-        <li>You may use the aforementioned <a href="http://httpd.apache.org/docs/apache_pb.gif">'Powered by Apache'
+        <li>You may use the aforementioned <a href="http://httpd.apache.org/apache_pb.gif">'Powered by Apache'
         graphic</a> or the <a href="http://www.apache.org/images/asf_logo.gif">Apache Software
         Foundation logo</a> in product description and promotional material
         <em>IF and ONLY IF</em> such use can in no way be interpreted as

Modified: httpd/httpd/trunk/docs/manual/faq/background.html.en
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/faq/background.html.en?rev=375322&r1=375321&r2=375322&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/faq/background.html.en (original)
+++ httpd/httpd/trunk/docs/manual/faq/background.html.en Mon Feb  6 09:55:59 2006
@@ -119,4 +119,4 @@
 </div><div id="footer">
 <p class="apache">Copyright 1995-2006 The Apache Software Foundation or its licensors, as applicable.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
 <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div>
-</body></html>
+</body></html>
\ No newline at end of file

Modified: httpd/httpd/trunk/docs/manual/mod/directives.html.de
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/directives.html.de?rev=375322&r1=375321&r2=375322&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/directives.html.de (original)
+++ httpd/httpd/trunk/docs/manual/mod/directives.html.de Mon Feb  6 09:55:59 2006
@@ -63,6 +63,7 @@
 <li><a href="mod_mime.html#addtype">AddType</a></li>
 <li><a href="mod_alias.html#alias">Alias</a></li>
 <li><a href="mod_alias.html#aliasmatch">AliasMatch</a></li>
+<li><a href="mod_access_compat.html#allow">Allow</a></li>
 <li><a href="mod_proxy.html#allowconnect">AllowCONNECT</a></li>
 <li><a href="core.html#allowencodedslashes">AllowEncodedSlashes</a></li>
 <li><a href="core.html#allowoverride">AllowOverride</a></li>
@@ -100,7 +101,7 @@
 <li><a href="mod_authnz_ldap.html#authldapurl">AuthLDAPUrl</a></li>
 <li><a href="core.html#authname">AuthName</a></li>
 <li><a href="mod_authn_core.html#authname">AuthName</a></li>
-<li><a href="mod_authn_alias.html#authnprovideralias">&lt;AuthnProviderAlias&gt;</a></li>
+<li><a href="mod_authn_core.html#authnprovideralias">&lt;AuthnProviderAlias&gt;</a></li>
 <li><a href="core.html#authtype">AuthType</a></li>
 <li><a href="mod_authn_core.html#authtype">AuthType</a></li>
 <li><a href="mod_authn_file.html#authuserfile">AuthUserFile</a></li>
@@ -124,6 +125,7 @@
 <li><a href="mod_cache.html#cachelastmodifiedfactor">CacheLastModifiedFactor</a></li>
 <li><a href="mod_cache.html#cachemaxexpire">CacheMaxExpire</a></li>
 <li><a href="mod_disk_cache.html#cachemaxfilesize">CacheMaxFileSize</a></li>
+<li><a href="mod_cache.html#cacheminexpire">CacheMinExpire</a></li>
 <li><a href="mod_disk_cache.html#cacheminfilesize">CacheMinFileSize</a></li>
 <li><a href="mod_negotiation.html#cachenegotiateddocs">CacheNegotiatedDocs</a></li>
 <li><a href="mod_disk_cache.html#cacheroot">CacheRoot</a></li>
@@ -165,6 +167,7 @@
 <li><a href="mod_deflate.html#deflatefilternote">DeflateFilterNote</a></li>
 <li><a href="mod_deflate.html#deflatememlevel">DeflateMemLevel</a></li>
 <li><a href="mod_deflate.html#deflatewindowsize">DeflateWindowSize</a></li>
+<li><a href="mod_access_compat.html#deny">Deny</a></li>
 <li><a href="core.html#directory">&lt;Directory&gt;</a></li>
 <li><a href="mod_dir.html#directoryindex">DirectoryIndex</a></li>
 <li><a href="core.html#directorymatch">&lt;DirectoryMatch&gt;</a></li>
@@ -279,6 +282,7 @@
 <li><a href="mod_nw_ssl.html#nwssltrustedcerts">NWSSLTrustedCerts</a></li>
 <li><a href="mod_nw_ssl.html#nwsslupgradeable">NWSSLUpgradeable</a></li>
 <li><a href="core.html#options" id="O" name="O">Options</a></li>
+<li><a href="mod_access_compat.html#order">Order</a></li>
 <li><a href="mod_env.html#passenv" id="P" name="P">PassEnv</a></li>
 <li><a href="mpm_common.html#pidfile">PidFile</a></li>
 <li><a href="mod_echo.html#protocolecho">ProtocolEcho</a></li>
@@ -330,6 +334,7 @@
 <li><a href="core.html#rlimitmem">RLimitMEM</a></li>
 <li><a href="core.html#rlimitnproc">RLimitNPROC</a></li>
 <li><a href="core.html#satisfy" id="S" name="S">Satisfy</a></li>
+<li><a href="mod_access_compat.html#satisfy">Satisfy</a></li>
 <li><a href="mod_authz_core.html#satisfyall">&lt;SatisfyAll&gt;</a></li>
 <li><a href="mod_authz_core.html#satisfyone">&lt;SatisfyOne&gt;</a></li>
 <li><a href="mpm_common.html#scoreboardfile">ScoreBoardFile</a></li>

Modified: httpd/httpd/trunk/docs/manual/mod/directives.html.es
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/directives.html.es?rev=375322&r1=375321&r2=375322&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/directives.html.es (original)
+++ httpd/httpd/trunk/docs/manual/mod/directives.html.es Mon Feb  6 09:55:59 2006
@@ -67,6 +67,7 @@
 <li><a href="mod_mime.html#addtype">AddType</a></li>
 <li><a href="mod_alias.html#alias">Alias</a></li>
 <li><a href="mod_alias.html#aliasmatch">AliasMatch</a></li>
+<li><a href="mod_access_compat.html#allow">Allow</a></li>
 <li><a href="mod_proxy.html#allowconnect">AllowCONNECT</a></li>
 <li><a href="core.html#allowencodedslashes">AllowEncodedSlashes</a></li>
 <li><a href="core.html#allowoverride">AllowOverride</a></li>
@@ -103,7 +104,7 @@
 <li><a href="mod_authnz_ldap.html#authldapremoteuserisdn">AuthLDAPRemoteUserIsDN</a></li>
 <li><a href="mod_authnz_ldap.html#authldapurl">AuthLDAPUrl</a></li>
 <li><a href="mod_authn_core.html#authname">AuthName</a></li>
-<li><a href="mod_authn_alias.html#authnprovideralias">&lt;AuthnProviderAlias&gt;</a></li>
+<li><a href="mod_authn_core.html#authnprovideralias">&lt;AuthnProviderAlias&gt;</a></li>
 <li><a href="mod_authn_core.html#authtype">AuthType</a></li>
 <li><a href="mod_authn_file.html#authuserfile">AuthUserFile</a></li>
 <li><a href="mod_authz_dbd.html#authzdbdlogintoreferer">AuthzDBDLoginToReferer</a></li>
@@ -126,6 +127,7 @@
 <li><a href="mod_cache.html#cachelastmodifiedfactor">CacheLastModifiedFactor</a></li>
 <li><a href="mod_cache.html#cachemaxexpire">CacheMaxExpire</a></li>
 <li><a href="mod_disk_cache.html#cachemaxfilesize">CacheMaxFileSize</a></li>
+<li><a href="mod_cache.html#cacheminexpire">CacheMinExpire</a></li>
 <li><a href="mod_disk_cache.html#cacheminfilesize">CacheMinFileSize</a></li>
 <li><a href="mod_negotiation.html#cachenegotiateddocs">CacheNegotiatedDocs</a></li>
 <li><a href="mod_disk_cache.html#cacheroot">CacheRoot</a></li>
@@ -167,6 +169,7 @@
 <li><a href="mod_deflate.html#deflatefilternote">DeflateFilterNote</a></li>
 <li><a href="mod_deflate.html#deflatememlevel">DeflateMemLevel</a></li>
 <li><a href="mod_deflate.html#deflatewindowsize">DeflateWindowSize</a></li>
+<li><a href="mod_access_compat.html#deny">Deny</a></li>
 <li><a href="core.html#directory">&lt;Directory&gt;</a></li>
 <li><a href="mod_dir.html#directoryindex">DirectoryIndex</a></li>
 <li><a href="core.html#directorymatch">&lt;DirectoryMatch&gt;</a></li>
@@ -282,6 +285,7 @@
 <li><a href="mod_nw_ssl.html#nwssltrustedcerts">NWSSLTrustedCerts</a></li>
 <li><a href="mod_nw_ssl.html#nwsslupgradeable">NWSSLUpgradeable</a></li>
 <li><a href="core.html#options" id="O" name="O">Options</a></li>
+<li><a href="mod_access_compat.html#order">Order</a></li>
 <li><a href="mod_env.html#passenv" id="P" name="P">PassEnv</a></li>
 <li><a href="mpm_common.html#pidfile">PidFile</a></li>
 <li><a href="mod_echo.html#protocolecho">ProtocolEcho</a></li>
@@ -332,7 +336,8 @@
 <li><a href="core.html#rlimitcpu">RLimitCPU</a></li>
 <li><a href="core.html#rlimitmem">RLimitMEM</a></li>
 <li><a href="core.html#rlimitnproc">RLimitNPROC</a></li>
-<li><a href="mod_authz_core.html#satisfyall" id="S" name="S">&lt;SatisfyAll&gt;</a></li>
+<li><a href="mod_access_compat.html#satisfy" id="S" name="S">Satisfy</a></li>
+<li><a href="mod_authz_core.html#satisfyall">&lt;SatisfyAll&gt;</a></li>
 <li><a href="mod_authz_core.html#satisfyone">&lt;SatisfyOne&gt;</a></li>
 <li><a href="mpm_common.html#scoreboardfile">ScoreBoardFile</a></li>
 <li><a href="mod_actions.html#script">Script</a></li>

Modified: httpd/httpd/trunk/docs/manual/mod/directives.html.ja.euc-jp
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/directives.html.ja.euc-jp?rev=375322&r1=375321&r2=375322&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/directives.html.ja.euc-jp [euc-jp] (original)
+++ httpd/httpd/trunk/docs/manual/mod/directives.html.ja.euc-jp [euc-jp] Mon Feb  6 09:55:59 2006
@@ -63,6 +63,7 @@
 <li><a href="mod_mime.html#addtype">AddType</a></li>
 <li><a href="mod_alias.html#alias">Alias</a></li>
 <li><a href="mod_alias.html#aliasmatch">AliasMatch</a></li>
+<li><a href="mod_access_compat.html#allow">Allow</a></li>
 <li><a href="mod_authz_host.html#allow">Allow</a></li>
 <li><a href="mod_proxy.html#allowconnect">AllowCONNECT</a></li>
 <li><a href="core.html#allowencodedslashes">AllowEncodedSlashes</a></li>
@@ -101,7 +102,7 @@
 <li><a href="mod_authnz_ldap.html#authldapurl">AuthLDAPUrl</a></li>
 <li><a href="core.html#authname">AuthName</a></li>
 <li><a href="mod_authn_core.html#authname">AuthName</a></li>
-<li><a href="mod_authn_alias.html#authnprovideralias">&lt;AuthnProviderAlias&gt;</a></li>
+<li><a href="mod_authn_core.html#authnprovideralias">&lt;AuthnProviderAlias&gt;</a></li>
 <li><a href="core.html#authtype">AuthType</a></li>
 <li><a href="mod_authn_core.html#authtype">AuthType</a></li>
 <li><a href="mod_authn_file.html#authuserfile">AuthUserFile</a></li>
@@ -169,6 +170,7 @@
 <li><a href="mod_deflate.html#deflatefilternote">DeflateFilterNote</a></li>
 <li><a href="mod_deflate.html#deflatememlevel">DeflateMemLevel</a></li>
 <li><a href="mod_deflate.html#deflatewindowsize">DeflateWindowSize</a></li>
+<li><a href="mod_access_compat.html#deny">Deny</a></li>
 <li><a href="mod_authz_host.html#deny">Deny</a></li>
 <li><a href="core.html#directory">&lt;Directory&gt;</a></li>
 <li><a href="mod_dir.html#directoryindex">DirectoryIndex</a></li>
@@ -284,6 +286,7 @@
 <li><a href="mod_nw_ssl.html#nwssltrustedcerts">NWSSLTrustedCerts</a></li>
 <li><a href="mod_nw_ssl.html#nwsslupgradeable">NWSSLUpgradeable</a></li>
 <li><a href="core.html#options" id="O" name="O">Options</a></li>
+<li><a href="mod_access_compat.html#order">Order</a></li>
 <li><a href="mod_authz_host.html#order">Order</a></li>
 <li><a href="mod_env.html#passenv" id="P" name="P">PassEnv</a></li>
 <li><a href="mpm_common.html#pidfile">PidFile</a></li>
@@ -336,6 +339,7 @@
 <li><a href="core.html#rlimitmem">RLimitMEM</a></li>
 <li><a href="core.html#rlimitnproc">RLimitNPROC</a></li>
 <li><a href="core.html#satisfy" id="S" name="S">Satisfy</a></li>
+<li><a href="mod_access_compat.html#satisfy">Satisfy</a></li>
 <li><a href="mod_authz_core.html#satisfyall">&lt;SatisfyAll&gt;</a></li>
 <li><a href="mod_authz_core.html#satisfyone">&lt;SatisfyOne&gt;</a></li>
 <li><a href="mpm_common.html#scoreboardfile">ScoreBoardFile</a></li>

Modified: httpd/httpd/trunk/docs/manual/mod/directives.html.ko.euc-kr
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/directives.html.ko.euc-kr?rev=375322&r1=375321&r2=375322&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/directives.html.ko.euc-kr [euc-kr] (original)
+++ httpd/httpd/trunk/docs/manual/mod/directives.html.ko.euc-kr [euc-kr] Mon Feb  6 09:55:59 2006
@@ -62,6 +62,7 @@
 <li><a href="mod_mime.html#addtype">AddType</a></li>
 <li><a href="mod_alias.html#alias">Alias</a></li>
 <li><a href="mod_alias.html#aliasmatch">AliasMatch</a></li>
+<li><a href="mod_access_compat.html#allow">Allow</a></li>
 <li><a href="mod_authz_host.html#allow">Allow</a></li>
 <li><a href="mod_proxy.html#allowconnect">AllowCONNECT</a></li>
 <li><a href="core.html#allowencodedslashes">AllowEncodedSlashes</a></li>
@@ -99,7 +100,7 @@
 <li><a href="mod_authnz_ldap.html#authldapremoteuserisdn">AuthLDAPRemoteUserIsDN</a></li>
 <li><a href="mod_authnz_ldap.html#authldapurl">AuthLDAPUrl</a></li>
 <li><a href="mod_authn_core.html#authname">AuthName</a></li>
-<li><a href="mod_authn_alias.html#authnprovideralias">&lt;AuthnProviderAlias&gt;</a></li>
+<li><a href="mod_authn_core.html#authnprovideralias">&lt;AuthnProviderAlias&gt;</a></li>
 <li><a href="mod_authn_core.html#authtype">AuthType</a></li>
 <li><a href="mod_authn_file.html#authuserfile">AuthUserFile</a></li>
 <li><a href="mod_authz_dbd.html#authzdbdlogintoreferer">AuthzDBDLoginToReferer</a></li>
@@ -164,6 +165,7 @@
 <li><a href="mod_deflate.html#deflatefilternote">DeflateFilterNote</a></li>
 <li><a href="mod_deflate.html#deflatememlevel">DeflateMemLevel</a></li>
 <li><a href="mod_deflate.html#deflatewindowsize">DeflateWindowSize</a></li>
+<li><a href="mod_access_compat.html#deny">Deny</a></li>
 <li><a href="mod_authz_host.html#deny">Deny</a></li>
 <li><a href="core.html#directory">&lt;Directory&gt;</a></li>
 <li><a href="mod_dir.html#directoryindex">DirectoryIndex</a></li>
@@ -280,6 +282,7 @@
 <li><a href="mod_nw_ssl.html#nwssltrustedcerts">NWSSLTrustedCerts</a></li>
 <li><a href="mod_nw_ssl.html#nwsslupgradeable">NWSSLUpgradeable</a></li>
 <li><a href="core.html#options" id="O" name="O">Options</a></li>
+<li><a href="mod_access_compat.html#order">Order</a></li>
 <li><a href="mod_authz_host.html#order">Order</a></li>
 <li><a href="mod_env.html#passenv" id="P" name="P">PassEnv</a></li>
 <li><a href="mpm_common.html#pidfile">PidFile</a></li>
@@ -331,7 +334,8 @@
 <li><a href="core.html#rlimitcpu">RLimitCPU</a></li>
 <li><a href="core.html#rlimitmem">RLimitMEM</a></li>
 <li><a href="core.html#rlimitnproc">RLimitNPROC</a></li>
-<li><a href="mod_authz_core.html#satisfyall" id="S" name="S">&lt;SatisfyAll&gt;</a></li>
+<li><a href="mod_access_compat.html#satisfy" id="S" name="S">Satisfy</a></li>
+<li><a href="mod_authz_core.html#satisfyall">&lt;SatisfyAll&gt;</a></li>
 <li><a href="mod_authz_core.html#satisfyone">&lt;SatisfyOne&gt;</a></li>
 <li><a href="mpm_common.html#scoreboardfile">ScoreBoardFile</a></li>
 <li><a href="mod_actions.html#script">Script</a></li>

Modified: httpd/httpd/trunk/docs/manual/mod/index.html.de
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/index.html.de?rev=375322&r1=375321&r2=375322&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/index.html.de (original)
+++ httpd/httpd/trunk/docs/manual/mod/index.html.de Mon Feb  6 09:55:59 2006
@@ -72,7 +72,9 @@
 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
 <div class="section"><h2><a id="other" name="other">Andere Module</a></h2>
 <p class="letters"><a href="#A">&nbsp;A&nbsp;</a> | <a href="#C">&nbsp;C&nbsp;</a> | <a href="#D">&nbsp;D&nbsp;</a> | <a href="#E">&nbsp;E&nbsp;</a> | <a href="#F">&nbsp;F&nbsp;</a> | <a href="#H">&nbsp;H&nbsp;</a> | <a href="#I">&nbsp;I&nbsp;</a> | <a href="#L">&nbsp;L&nbsp;</a> | <a href="#M">&nbsp;M&nbsp;</a> | <a href="#N">&nbsp;N&nbsp;</a> | <a href="#P">&nbsp;P&nbsp;</a> | <a href="#R">&nbsp;R&nbsp;</a> | <a href="#S">&nbsp;S&nbsp;</a> | <a href="#U">&nbsp;U&nbsp;</a> | <a href="#V">&nbsp;V&nbsp;</a></p>
-<dl><dt><a href="mod_actions.html" id="A" name="A">mod_actions</a></dt><dd>Dieses Modul ermöglicht die Ausführung von CGI-Skripten
+<dl><dt><a href="mod_access_compat.html" id="A" name="A">mod_access_compat</a></dt><dd>Group authorizations based on host (name or IP
+address)</dd>
+<dt><a href="mod_actions.html">mod_actions</a></dt><dd>Dieses Modul ermöglicht die Ausführung von CGI-Skripten
   in Abhängigkeit von Medientypen und Anfragemethoden.</dd>
 <dt><a href="mod_alias.html">mod_alias</a></dt><dd>Provides for mapping different parts of the host
     filesystem in the document tree and for URL redirection</dd>
@@ -81,8 +83,6 @@
 <dt><a href="mod_auth_basic.html">mod_auth_basic</a></dt><dd>Basic authentication</dd>
 <dt><a href="mod_auth_digest.html">mod_auth_digest</a></dt><dd>User authentication using MD5
     Digest Authentication.</dd>
-<dt><a href="mod_authn_alias.html">mod_authn_alias</a></dt><dd>Provides the ability to create extended authentication 
-    providers based on actual providers</dd>
 <dt><a href="mod_authn_anon.html">mod_authn_anon</a></dt><dd>Allows "anonymous" user access to authenticated
     areas</dd>
 <dt><a href="mod_authn_core.html">mod_authn_core</a></dt><dd>Core Authentication</dd>

Modified: httpd/httpd/trunk/docs/manual/mod/index.html.es
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/index.html.es?rev=375322&r1=375321&r2=375322&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/index.html.es (original)
+++ httpd/httpd/trunk/docs/manual/mod/index.html.es Mon Feb  6 09:55:59 2006
@@ -73,7 +73,9 @@
 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
 <div class="section"><h2><a id="other" name="other">Otros Módulos</a></h2>
 <p class="letters"><a href="#A">&nbsp;A&nbsp;</a> | <a href="#C">&nbsp;C&nbsp;</a> | <a href="#D">&nbsp;D&nbsp;</a> | <a href="#E">&nbsp;E&nbsp;</a> | <a href="#F">&nbsp;F&nbsp;</a> | <a href="#H">&nbsp;H&nbsp;</a> | <a href="#I">&nbsp;I&nbsp;</a> | <a href="#L">&nbsp;L&nbsp;</a> | <a href="#M">&nbsp;M&nbsp;</a> | <a href="#N">&nbsp;N&nbsp;</a> | <a href="#P">&nbsp;P&nbsp;</a> | <a href="#R">&nbsp;R&nbsp;</a> | <a href="#S">&nbsp;S&nbsp;</a> | <a href="#U">&nbsp;U&nbsp;</a> | <a href="#V">&nbsp;V&nbsp;</a></p>
-<dl><dt><a href="mod_actions.html" id="A" name="A">mod_actions</a></dt><dd>This module provides for executing CGI scripts based on
+<dl><dt><a href="mod_access_compat.html" id="A" name="A">mod_access_compat</a></dt><dd>Group authorizations based on host (name or IP
+address)</dd>
+<dt><a href="mod_actions.html">mod_actions</a></dt><dd>This module provides for executing CGI scripts based on
 media type or request method.</dd>
 <dt><a href="mod_alias.html">mod_alias</a></dt><dd>Provides for mapping different parts of the host
     filesystem in the document tree and for URL redirection</dd>
@@ -82,8 +84,6 @@
 <dt><a href="mod_auth_basic.html">mod_auth_basic</a></dt><dd>Basic authentication</dd>
 <dt><a href="mod_auth_digest.html">mod_auth_digest</a></dt><dd>User authentication using MD5
     Digest Authentication.</dd>
-<dt><a href="mod_authn_alias.html">mod_authn_alias</a></dt><dd>Provides the ability to create extended authentication 
-    providers based on actual providers</dd>
 <dt><a href="mod_authn_anon.html">mod_authn_anon</a></dt><dd>Allows "anonymous" user access to authenticated
     areas</dd>
 <dt><a href="mod_authn_core.html">mod_authn_core</a></dt><dd>Core Authentication</dd>

Modified: httpd/httpd/trunk/docs/manual/mod/index.html.ja.euc-jp
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/index.html.ja.euc-jp?rev=375322&r1=375321&r2=375322&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/index.html.ja.euc-jp [euc-jp] (original)
+++ httpd/httpd/trunk/docs/manual/mod/index.html.ja.euc-jp [euc-jp] Mon Feb  6 09:55:59 2006
@@ -68,7 +68,9 @@
 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
 <div class="section"><h2><a id="other" name="other">他のモジュール</a></h2>
 <p class="letters"><a href="#A">&nbsp;A&nbsp;</a> | <a href="#C">&nbsp;C&nbsp;</a> | <a href="#D">&nbsp;D&nbsp;</a> | <a href="#E">&nbsp;E&nbsp;</a> | <a href="#F">&nbsp;F&nbsp;</a> | <a href="#H">&nbsp;H&nbsp;</a> | <a href="#I">&nbsp;I&nbsp;</a> | <a href="#L">&nbsp;L&nbsp;</a> | <a href="#M">&nbsp;M&nbsp;</a> | <a href="#N">&nbsp;N&nbsp;</a> | <a href="#P">&nbsp;P&nbsp;</a> | <a href="#R">&nbsp;R&nbsp;</a> | <a href="#S">&nbsp;S&nbsp;</a> | <a href="#U">&nbsp;U&nbsp;</a> | <a href="#V">&nbsp;V&nbsp;</a></p>
-<dl><dt><a href="mod_actions.html" id="A" name="A">mod_actions</a></dt><dd>メディアタイプやリクエストメソッドに応じて
+<dl><dt><a href="mod_access_compat.html" id="A" name="A">mod_access_compat</a></dt><dd>Group authorizations based on host (name or IP
+address)</dd>
+<dt><a href="mod_actions.html">mod_actions</a></dt><dd>メディアタイプやリクエストメソッドに応じて
 CGI スクリプトを実行する機能を提供</dd>
 <dt><a href="mod_alias.html">mod_alias</a></dt><dd>ホストファイルシステム上のいろいろな違う場所を
     ドキュメントツリーにマップする機能と、
@@ -77,8 +79,6 @@
 <dt><a href="mod_auth_basic.html">mod_auth_basic</a></dt><dd>基本認証</dd>
 <dt><a href="mod_auth_digest.html">mod_auth_digest</a></dt><dd>User authentication using MD5
     Digest Authentication.</dd>
-<dt><a href="mod_authn_alias.html">mod_authn_alias</a></dt><dd>Provides the ability to create extended authentication 
-    providers based on actual providers</dd>
 <dt><a href="mod_authn_anon.html">mod_authn_anon</a></dt><dd>認証が必要な領域への "anonymous" ユーザのアクセスを許可する
 </dd>
 <dt><a href="mod_authn_core.html">mod_authn_core</a></dt><dd>Core Authentication</dd>

Modified: httpd/httpd/trunk/docs/manual/mod/index.html.ko.euc-kr
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/index.html.ko.euc-kr?rev=375322&r1=375321&r2=375322&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/index.html.ko.euc-kr [euc-kr] (original)
+++ httpd/httpd/trunk/docs/manual/mod/index.html.ko.euc-kr [euc-kr] Mon Feb  6 09:55:59 2006
@@ -65,15 +65,15 @@
 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
 <div class="section"><h2><a id="other" name="other">다른 모듈</a></h2>
 <p class="letters"><a href="#A">&nbsp;A&nbsp;</a> | <a href="#C">&nbsp;C&nbsp;</a> | <a href="#D">&nbsp;D&nbsp;</a> | <a href="#E">&nbsp;E&nbsp;</a> | <a href="#F">&nbsp;F&nbsp;</a> | <a href="#H">&nbsp;H&nbsp;</a> | <a href="#I">&nbsp;I&nbsp;</a> | <a href="#L">&nbsp;L&nbsp;</a> | <a href="#M">&nbsp;M&nbsp;</a> | <a href="#N">&nbsp;N&nbsp;</a> | <a href="#P">&nbsp;P&nbsp;</a> | <a href="#R">&nbsp;R&nbsp;</a> | <a href="#S">&nbsp;S&nbsp;</a> | <a href="#U">&nbsp;U&nbsp;</a> | <a href="#V">&nbsp;V&nbsp;</a></p>
-<dl><dt><a href="mod_actions.html" id="A" name="A">mod_actions</a></dt><dd>이 모듈은 미디어종류나 요청메서드에 따라 CGI
+<dl><dt><a href="mod_access_compat.html" id="A" name="A">mod_access_compat</a></dt><dd>Group authorizations based on host (name or IP
+address)</dd>
+<dt><a href="mod_actions.html">mod_actions</a></dt><dd>이 모듈은 미디어종류나 요청메서드에 따라 CGI
 스크립트를 실행한다.</dd>
 <dt><a href="mod_alias.html">mod_alias</a></dt><dd>파일시스템의 다른 부분들을 문서 계층구조에 포함하고,
     URL 리다이렉션을 제공한다</dd>
 <dt><a href="mod_asis.html">mod_asis</a></dt><dd>HTTP 헤더를 포함한 파일을 보낸다</dd>
 <dt><a href="mod_auth_basic.html">mod_auth_basic</a></dt><dd>Basic authentication</dd>
 <dt><a href="mod_auth_digest.html">mod_auth_digest</a></dt><dd>MD5 Digest Authentication을 사용한 사용자인증.</dd>
-<dt><a href="mod_authn_alias.html">mod_authn_alias</a></dt><dd>Provides the ability to create extended authentication 
-    providers based on actual providers</dd>
 <dt><a href="mod_authn_anon.html">mod_authn_anon</a></dt><dd>인증영역에 "익명(anonymous)" 사용자의 접근을
 허용한다</dd>
 <dt><a href="mod_authn_core.html">mod_authn_core</a></dt><dd>Core Authentication</dd>

Added: httpd/httpd/trunk/docs/manual/mod/mod_access_compat.html
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/mod_access_compat.html?rev=375322&view=auto
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_access_compat.html (added)
+++ httpd/httpd/trunk/docs/manual/mod/mod_access_compat.html Mon Feb  6 09:55:59 2006
@@ -0,0 +1,3 @@
+URI: mod_access_compat.html.en
+Content-Language: en
+Content-type: text/html; charset=ISO-8859-1

Propchange: httpd/httpd/trunk/docs/manual/mod/mod_access_compat.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: httpd/httpd/trunk/docs/manual/mod/mod_access_compat.html.en
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/mod_access_compat.html.en?rev=375322&view=auto
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_access_compat.html.en (added)
+++ httpd/httpd/trunk/docs/manual/mod/mod_access_compat.html.en Mon Feb  6 09:55:59 2006
@@ -0,0 +1,388 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!--
+        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+              This file is generated from xml source: DO NOT EDIT
+        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+      -->
+<title>mod_access_compat - Apache HTTP Server</title>
+<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
+<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
+<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" />
+<link href="../images/favicon.ico" rel="shortcut icon" /></head>
+<body>
+<div id="page-header">
+<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p>
+<p class="apache">Apache HTTP Server Version 2.3</p>
+<img alt="" src="../images/feather.gif" /></div>
+<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
+<div id="path">
+<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">HTTP Server</a> &gt; <a href="http://httpd.apache.org/docs/">Documentation</a> &gt; <a href="../">Version 2.3</a> &gt; <a href="./">Modules</a></div>
+<div id="page-content">
+<div id="preamble"><h1>Apache Module mod_access_compat</h1>
+<div class="toplang">
+<p><span>Available Languages: </span><a href="../en/mod/mod_access_compat.html" title="English">&nbsp;en&nbsp;</a></p>
+</div>
+<table class="module"><tr><th><a href="module-dict.html#Description">Description:</a></th><td>Group authorizations based on host (name or IP
+address)</td></tr>
+<tr><th><a href="module-dict.html#Status">Status:</a></th><td>Extension</td></tr>
+<tr><th><a href="module-dict.html#ModuleIdentifier">Module Identifier:</a></th><td>access_compat_module</td></tr>
+<tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_access_compat.c</td></tr>
+<tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache 2.3 as a compatibility module with 
+previous versions of Apache 2.x.  The directives provided by this module
+have been deprecated by the new authz refactoring.  Please see 
+<code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code></td></tr></table>
+<h3>Summary</h3>
+
+    <p>The directives provided by <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> are
+    used in <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code>,
+    <code class="directive"><a href="../mod/core.html#files">&lt;Files&gt;</a></code>, and
+    <code class="directive"><a href="../mod/core.html#location">&lt;Location&gt;</a></code> sections
+    as well as <code><a href="core.html#accessfilename">.htaccess</a>
+    </code> files to control access to particular parts of the server.
+    Access can be controlled based on the client hostname, IP address, or
+    other characteristics of the client request, as captured in <a href="../env.html">environment variables</a>. The <code class="directive"><a href="#allow">Allow</a></code> and <code class="directive"><a href="#deny">Deny</a></code> directives are used to
+    specify which clients are or are not allowed access to the server,
+    while the <code class="directive"><a href="#order">Order</a></code>
+    directive sets the default access state, and configures how the
+    <code class="directive"><a href="#allow">Allow</a></code> and <code class="directive"><a href="#deny">Deny</a></code> directives interact with each
+    other.</p>
+
+    <p>Both host-based access restrictions and password-based
+    authentication may be implemented simultaneously. In that case,
+    the <code class="directive"><a href="../mod/core.html#satisfy">Satisfy</a></code> directive is used
+    to determine how the two sets of restrictions interact.</p>
+
+    <div class="warning"><h3>Note</h3>
+      <p>The directives provided by <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> have
+      been deprecated by the new authz refactoring. Please see 
+      <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code>.  The module 
+      <code class="module"><a href="../mod/mod_authz_default.html">mod_authz_default</a></code> must also be loaded to provide for
+      default authorization handling.</p>
+    </div>
+
+    <p>In general, access restriction directives apply to all
+    access methods (<code>GET</code>, <code>PUT</code>,
+    <code>POST</code>, 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 <code class="directive"><a href="../mod/core.html#limit">&lt;Limit&gt;</a></code> section.</p>
+</div>
+<div id="quickview"><h3 class="directives">Directives</h3>
+<ul id="toc">
+<li><img alt="" src="../images/down.gif" /> <a href="#allow">Allow</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#deny">Deny</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#order">Order</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#satisfy">Satisfy</a></li>
+</ul>
+<h3>See also</h3>
+<ul class="seealso">
+<li><code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code></li>
+<li><code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code></li>
+<li><code class="module"><a href="../mod/mod_authz_core.html">mod_authz_core</a></code></li>
+</ul></div>
+
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="directive-section"><h2><a name="Allow" id="Allow">Allow</a> <a name="allow" id="allow">Directive</a></h2>
+<table class="directive">
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Controls which hosts can access an area of the
+server</td></tr>
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> Allow from all|<var>host</var>|env=<var>env-variable</var>
+[<var>host</var>|env=<var>env-variable</var>] ...</code></td></tr>
+<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr>
+<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>Limit</td></tr>
+<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
+<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr>
+</table>
+    <p>The <code class="directive">Allow</code> directive affects 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.</p>
+
+    <p>The first argument to this directive is always
+    <code>from</code>. The subsequent arguments can take three
+    different forms. If <code>Allow from all</code> is specified, then
+    all hosts are allowed access, subject to the configuration of the
+    <code class="directive"><a href="#deny">Deny</a></code> and <code class="directive"><a href="#order">Order</a></code> directives as discussed
+    below. To allow only particular hosts or groups of hosts to access
+    the server, the <em>host</em> can be specified in any of the
+    following formats:</p>
+
+    <dl>
+      <dt>A (partial) domain-name</dt>
+
+      <dd>
+      <div class="example"><h3>Example:</h3><p><code>
+        Allow from apache.org<br />
+        Allow from .net example.edu
+      </code></p></div>
+      <p>Hosts whose names match, or end in, this string are allowed
+      access. Only complete components are matched, so the above
+      example will match <code>foo.apache.org</code> but it will not
+      match <code>fooapache.org</code>. This configuration will cause
+      Apache to perform a double reverse DNS lookup on the client IP
+      address, regardless of the setting of the <code class="directive"><a href="../mod/core.html#hostnamelookups">HostnameLookups</a></code> 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.</p></dd>
+
+      <dt>A full IP address</dt>
+
+      <dd>
+      <div class="example"><h3>Example:</h3><p><code>
+        Allow from 10.1.2.3<br />
+        Allow from 192.168.1.104 192.168.1.205
+      </code></p></div>
+      <p>An IP address of a host allowed access</p></dd>
+
+      <dt>A partial IP address</dt>
+
+      <dd>
+      <div class="example"><h3>Example:</h3><p><code>
+        Allow from 10.1<br />
+        Allow from 10 172.20 192.168.2
+      </code></p></div>
+      <p>The first 1 to 3 bytes of an IP address, for subnet
+      restriction.</p></dd>
+
+      <dt>A network/netmask pair</dt>
+
+      <dd>
+      <div class="example"><h3>Example:</h3><p><code>
+        Allow from 10.1.0.0/255.255.0.0
+      </code></p></div>
+      <p>A network a.b.c.d, and a netmask w.x.y.z. For more
+      fine-grained subnet restriction.</p></dd>
+
+      <dt>A network/nnn CIDR specification</dt>
+
+      <dd>
+      <div class="example"><h3>Example:</h3><p><code>
+        Allow from 10.1.0.0/16
+      </code></p></div>
+      <p>Similar to the previous case, except the netmask consists of
+      nnn high-order 1 bits.</p></dd>
+    </dl>
+
+    <p>Note that the last three examples above match exactly the
+    same set of hosts.</p>
+
+    <p>IPv6 addresses and IPv6 subnets can be specified as shown
+    below:</p>
+
+    <div class="example"><p><code>
+       Allow from 2001:db8::a00:20ff:fea7:ccea<br />
+       Allow from 2001:db8::a00:20ff:fea7:ccea/10
+    </code></p></div>
+
+    <p>The third format of the arguments to the
+    <code class="directive">Allow</code> directive allows access to the server
+    to be controlled based on the existence of an <a href="../env.html">environment variable</a>. When <code>Allow from
+    env=<var>env-variable</var></code> is specified, then the request is
+    allowed access if the environment variable <var>env-variable</var>
+    exists. The server provides the ability to set environment
+    variables in a flexible way based on characteristics of the client
+    request using the directives provided by
+    <code class="module"><a href="../mod/mod_setenvif.html">mod_setenvif</a></code>. Therefore, this directive can be
+    used to allow access based on such factors as the clients
+    <code>User-Agent</code> (browser type), <code>Referer</code>, or
+    other HTTP request header fields.</p>
+
+    <div class="example"><h3>Example:</h3><p><code>
+      SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in<br />
+      &lt;Directory /docroot&gt;<br />
+      <span class="indent">
+        Order Deny,Allow<br />
+        Deny from all<br />
+        Allow from env=let_me_in<br />
+      </span>
+      &lt;/Directory&gt;
+    </code></p></div>
+
+    <p>In this case, browsers with a user-agent string beginning
+    with <code>KnockKnock/2.0</code> will be allowed access, and all
+    others will be denied.</p>
+
+</div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="directive-section"><h2><a name="Deny" id="Deny">Deny</a> <a name="deny" id="deny">Directive</a></h2>
+<table class="directive">
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Controls which hosts are denied access to the
+server</td></tr>
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> Deny from all|<var>host</var>|env=<var>env-variable</var>
+[<var>host</var>|env=<var>env-variable</var>] ...</code></td></tr>
+<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr>
+<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>Limit</td></tr>
+<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
+<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr>
+</table>
+    <p>This directive allows access to the server to be restricted
+    based on hostname, IP address, or environment variables. The
+    arguments for the <code class="directive">Deny</code> directive are
+    identical to the arguments for the <code class="directive"><a href="#allow">Allow</a></code> directive.</p>
+
+</div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="directive-section"><h2><a name="Order" id="Order">Order</a> <a name="order" id="order">Directive</a></h2>
+<table class="directive">
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Controls the default access state and the order in which
+<code class="directive">Allow</code> and <code class="directive">Deny</code> are
+evaluated.</td></tr>
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> Order <var>ordering</var></code></td></tr>
+<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>Order Deny,Allow</code></td></tr>
+<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr>
+<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>Limit</td></tr>
+<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
+<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr>
+</table>
+    <p>The <code class="directive">Order</code> directive controls the default
+    access state and the order in which <code class="directive"><a href="#allow">Allow</a></code> and <code class="directive"><a href="#deny">Deny</a></code> directives are evaluated.
+    <var>Ordering</var> is one of</p>
+
+    <dl>
+      <dt><code>Deny,Allow</code></dt>
+
+      <dd>The <code class="directive"><a href="#deny">Deny</a></code> directives
+      are evaluated before the <code class="directive"><a href="#allow">Allow</a></code> directives. Access is
+      allowed by default. Any client which does not match a
+      <code class="directive"><a href="#deny">Deny</a></code> directive or does
+      match an <code class="directive"><a href="#allow">Allow</a></code>
+      directive will be allowed access to the server.</dd>
+
+      <dt><code>Allow,Deny</code></dt>
+
+      <dd>The <code class="directive"><a href="#allow">Allow</a></code>
+      directives are evaluated before the <code class="directive"><a href="#deny">Deny</a></code> directives. Access is denied
+      by default. Any client which does not match an <code class="directive"><a href="#allow">Allow</a></code> directive or does match a
+      <code class="directive"><a href="#deny">Deny</a></code> directive will be
+      denied access to the server.</dd>
+
+      <dt><code>Mutual-failure</code></dt>
+
+      <dd>Only those hosts which appear on the <code class="directive"><a href="#allow">Allow</a></code> list and do not appear on
+      the <code class="directive"><a href="#deny">Deny</a></code> list are
+      granted access. This ordering has the same effect as <code>Order
+      Allow,Deny</code> and is deprecated in favor of that
+      configuration.</dd>
+    </dl>
+
+    <p>Keywords may only be separated by a comma; <em>no whitespace</em> is
+    allowed between them. Note that in all cases every <code class="directive"><a href="#allow">Allow</a></code> and <code class="directive"><a href="#deny">Deny</a></code> statement is evaluated.</p>
+
+    <p>In the following example, all hosts in the apache.org domain
+    are allowed access; all other hosts are denied access.</p>
+
+    <div class="example"><p><code>
+      Order Deny,Allow<br />
+      Deny from all<br />
+      Allow from apache.org
+    </code></p></div>
+
+    <p>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.</p>
+
+    <div class="example"><p><code>
+      Order Allow,Deny<br />
+      Allow from apache.org<br />
+      Deny from foo.apache.org
+    </code></p></div>
+
+    <p>On the other hand, if the <code class="directive">Order</code> in the last
+    example is changed to <code>Deny,Allow</code>, all hosts will
+    be allowed access. This happens because, regardless of the
+    actual ordering of the directives in the configuration file,
+    the <code>Allow from apache.org</code> will be evaluated last
+    and will override the <code>Deny from foo.apache.org</code>.
+    All hosts not in the <code>apache.org</code> domain will also
+    be allowed access because the default state will change to
+    <em>allow</em>.</p>
+
+    <p>The presence of an <code class="directive">Order</code> directive can affect
+    access to a part of the server even in the absence of accompanying
+    <code class="directive"><a href="#allow">Allow</a></code> and <code class="directive"><a href="#deny">Deny</a></code> directives because of its effect
+    on the default access state. For example,</p>
+
+    <div class="example"><p><code>
+      &lt;Directory /www&gt;<br />
+      <span class="indent">
+        Order Allow,Deny<br />
+      </span>
+      &lt;/Directory&gt;
+    </code></p></div>
+
+    <p>will deny all access to the <code>/www</code> directory
+    because the default access state will be set to
+    <em>deny</em>.</p>
+
+    <p>The <code class="directive">Order</code> directive controls the order of access
+    directive processing only within each phase of the server's
+    configuration processing. This implies, for example, that an
+    <code class="directive"><a href="#allow">Allow</a></code> or <code class="directive"><a href="#deny">Deny</a></code> directive occurring in a
+    <code class="directive"><a href="../mod/core.html#location">&lt;Location&gt;</a></code> section will
+    always be evaluated after an <code class="directive"><a href="#allow">Allow</a></code> or <code class="directive"><a href="#deny">Deny</a></code> directive occurring in a
+    <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> section or
+    <code>.htaccess</code> file, regardless of the setting of the
+    <code class="directive">Order</code> directive. For details on the merging
+    of configuration sections, see the documentation on <a href="../sections.html">How Directory, Location and Files sections
+    work</a>.</p>
+
+</div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="directive-section"><h2><a name="Satisfy" id="Satisfy">Satisfy</a> <a name="satisfy" id="satisfy">Directive</a></h2>
+<table class="directive">
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Interaction between host-level access control and
+user authentication</td></tr>
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>Satisfy Any|All</code></td></tr>
+<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>Satisfy All</code></td></tr>
+<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr>
+<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>AuthConfig</td></tr>
+<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
+<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr>
+<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Influenced by <code class="directive"><a href="../mod/core.html#limit">&lt;Limit&gt;</a></code> and <code class="directive"><a href="../mod/core.html#limitexcept">&lt;LimitExcept&gt;</a></code> in version 2.0.51 and
+later</td></tr>
+</table>
+    <p>Access policy if both <code class="directive"><a href="../mod/mod_authz_host.html#allow">Allow</a></code> and <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> used. The parameter can be
+    either <code>All</code> or <code>Any</code>. This directive is only
+    useful if access to a particular area is being restricted by both
+    username/password <em>and</em> client host address. In this case
+    the default behavior (<code>All</code>) is to require that the client
+    passes the address access restriction <em>and</em> enters a valid
+    username and password. With the <code>Any</code> option the client will be
+    granted access if they either pass the host restriction or enter a
+    valid username and password. This can be used to password restrict
+    an area, but to let clients from particular addresses in without
+    prompting for a password.</p>
+
+    <p>For example, if you wanted to let people on your network have
+    unrestricted access to a portion of your website, but require that
+    people outside of your network provide a password, you could use a
+    configuration similar to the following:</p>
+
+    <div class="example"><p><code>
+      Require valid-user<br />
+      Allow from 192.168.1<br />
+      Satisfy Any
+    </code></p></div>
+
+    <p>Since version 2.0.51 <code class="directive">Satisfy</code> directives can
+    be restricted to particular methods by <code class="directive"><a href="../mod/core.html#limit">&lt;Limit&gt;</a></code> and <code class="directive"><a href="../mod/core.html#limitexcept">&lt;LimitExcept&gt;</a></code> sections.</p>
+
+<h3>See also</h3>
+<ul>
+<li><code class="directive"><a href="#allow">Allow</a></code></li>
+<li><code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code></li>
+</ul>
+</div>
+</div>
+<div class="bottomlang">
+<p><span>Available Languages: </span><a href="../en/mod/mod_access_compat.html" title="English">&nbsp;en&nbsp;</a></p>
+</div><div id="footer">
+<p class="apache">Copyright 1995-2006 The Apache Software Foundation or its licensors, as applicable.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
+<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div>
+</body></html>
\ No newline at end of file

Propchange: httpd/httpd/trunk/docs/manual/mod/mod_access_compat.html.en
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: httpd/httpd/trunk/docs/manual/mod/mod_access_compat.xml
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/mod_access_compat.xml?rev=375322&r1=375321&r2=375322&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_access_compat.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_access_compat.xml Mon Feb  6 09:55:59 2006
@@ -1,397 +1,397 @@
-<?xml version="1.0"?>
-<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
-<?xml-stylesheet type="text/xsl" href="../style/manual.en.xsl"?>
-<!-- $LastChangedRevision: 327999 $ -->
-
-<!--
- Copyright 2002-2005 The Apache Software Foundation or its licensors, as
- applicable.
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-
-<modulesynopsis metafile="mod_access_compat.xml.meta">
-
-<name>mod_access_compat</name> 
-<description>Group authorizations based on host (name or IP
-address)</description>
-<status>Extension</status>
-<sourcefile>mod_access_compat.c</sourcefile>
-<identifier>access_compat_module</identifier>
-<compatibility>Available in Apache 2.3 as a compatibility module with 
-previous versions of Apache 2.x.  The directives provided by this module
-have been deprecated by the new authz refactoring.  Please see 
-<module>mod_authz_host</module></compatibility>
-
-<summary>
-    <p>The directives provided by <module>mod_access_compat</module> are
-    used in <directive module="core" type="section">Directory</directive>,
-    <directive module="core" type="section">Files</directive>, and
-    <directive module="core" type="section">Location</directive> sections
-    as well as <code><a href="core.html#accessfilename">.htaccess</a>
-    </code> files to control access to particular parts of the server.
-    Access can be controlled based on the client hostname, IP address, or
-    other characteristics of the client request, as captured in <a
-    href="../env.html">environment variables</a>. The <directive
-    module="mod_access_compat">Allow</directive> and <directive
-    module="mod_access_compat">Deny</directive> directives are used to
-    specify which clients are or are not allowed access to the server,
-    while the <directive module="mod_access_compat">Order</directive>
-    directive sets the default access state, and configures how the
-    <directive module="mod_access_compat">Allow</directive> and <directive
-    module="mod_access_compat">Deny</directive> directives interact with each
-    other.</p>
-
-    <p>Both host-based access restrictions and password-based
-    authentication may be implemented simultaneously. In that case,
-    the <directive module="core">Satisfy</directive> directive is used
-    to determine how the two sets of restrictions interact.</p>
-
-    <note type="warning"><title>Note</title>
-      <p>The directives provided by <module>mod_access_compat</module> have
-      been deprecated by the new authz refactoring. Please see 
-      <module>mod_authz_host</module>.  The module 
-      <module>mod_authz_default</module> must also be loaded to provide for
-      default authorization handling.</p>
-    </note>
-
-    <p>In general, access restriction directives apply to all
-    access methods (<code>GET</code>, <code>PUT</code>,
-    <code>POST</code>, 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 <directive module="core" type="section">Limit</directive> section.</p>
-</summary>
-
-<seealso><directive module="mod_authz_core">Require</directive></seealso>
-<seealso><module>mod_authz_host</module></seealso>
-<seealso><module>mod_authz_core</module></seealso>
-
-<directivesynopsis>
-<name>Allow</name>
-<description>Controls which hosts can access an area of the
-server</description>
-<syntax> Allow from all|<var>host</var>|env=<var>env-variable</var>
-[<var>host</var>|env=<var>env-variable</var>] ...</syntax>
-<contextlist><context>directory</context><context>.htaccess</context>
-</contextlist>
-<override>Limit</override>
-
-<usage>
-    <p>The <directive>Allow</directive> directive affects 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.</p>
-
-    <p>The first argument to this directive is always
-    <code>from</code>. The subsequent arguments can take three
-    different forms. If <code>Allow from all</code> is specified, then
-    all hosts are allowed access, subject to the configuration of the
-    <directive module="mod_access_compat">Deny</directive> and <directive
-    module="mod_access_compat">Order</directive> directives as discussed
-    below. To allow only particular hosts or groups of hosts to access
-    the server, the <em>host</em> can be specified in any of the
-    following formats:</p>
-
-    <dl>
-      <dt>A (partial) domain-name</dt>
-
-      <dd>
-      <example><title>Example:</title>
-        Allow from apache.org<br />
-        Allow from .net example.edu
-      </example>
-      <p>Hosts whose names match, or end in, this string are allowed
-      access. Only complete components are matched, so the above
-      example will match <code>foo.apache.org</code> but it will not
-      match <code>fooapache.org</code>. This configuration will cause
-      Apache to perform a double reverse DNS lookup on the client IP
-      address, regardless of the setting of the <directive
-      module="core">HostnameLookups</directive> 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.</p></dd>
-
-      <dt>A full IP address</dt>
-
-      <dd>
-      <example><title>Example:</title>
-        Allow from 10.1.2.3<br />
-        Allow from 192.168.1.104 192.168.1.205
-      </example>
-      <p>An IP address of a host allowed access</p></dd>
-
-      <dt>A partial IP address</dt>
-
-      <dd>
-      <example><title>Example:</title>
-        Allow from 10.1<br />
-        Allow from 10 172.20 192.168.2
-      </example>
-      <p>The first 1 to 3 bytes of an IP address, for subnet
-      restriction.</p></dd>
-
-      <dt>A network/netmask pair</dt>
-
-      <dd>
-      <example><title>Example:</title>
-        Allow from 10.1.0.0/255.255.0.0
-      </example>
-      <p>A network a.b.c.d, and a netmask w.x.y.z. For more
-      fine-grained subnet restriction.</p></dd>
-
-      <dt>A network/nnn CIDR specification</dt>
-
-      <dd>
-      <example><title>Example:</title>
-        Allow from 10.1.0.0/16
-      </example>
-      <p>Similar to the previous case, except the netmask consists of
-      nnn high-order 1 bits.</p></dd>
-    </dl>
-
-    <p>Note that the last three examples above match exactly the
-    same set of hosts.</p>
-
-    <p>IPv6 addresses and IPv6 subnets can be specified as shown
-    below:</p>
-
-    <example>
-       Allow from 2001:db8::a00:20ff:fea7:ccea<br />
-       Allow from 2001:db8::a00:20ff:fea7:ccea/10
-    </example>
-
-    <p>The third format of the arguments to the
-    <directive>Allow</directive> directive allows access to the server
-    to be controlled based on the existence of an <a
-    href="../env.html">environment variable</a>. When <code>Allow from
-    env=<var>env-variable</var></code> is specified, then the request is
-    allowed access if the environment variable <var>env-variable</var>
-    exists. The server provides the ability to set environment
-    variables in a flexible way based on characteristics of the client
-    request using the directives provided by
-    <module>mod_setenvif</module>. Therefore, this directive can be
-    used to allow access based on such factors as the clients
-    <code>User-Agent</code> (browser type), <code>Referer</code>, or
-    other HTTP request header fields.</p>
-
-    <example><title>Example:</title>
-      SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in<br />
-      &lt;Directory /docroot&gt;<br />
-      <indent>
-        Order Deny,Allow<br />
-        Deny from all<br />
-        Allow from env=let_me_in<br />
-      </indent>
-      &lt;/Directory&gt;
-    </example>
-
-    <p>In this case, browsers with a user-agent string beginning
-    with <code>KnockKnock/2.0</code> will be allowed access, and all
-    others will be denied.</p>
-</usage>
-</directivesynopsis>
-
-<directivesynopsis>
-<name>Deny</name>
-<description>Controls which hosts are denied access to the
-server</description>
-<syntax> Deny from all|<var>host</var>|env=<var>env-variable</var>
-[<var>host</var>|env=<var>env-variable</var>] ...</syntax>
-<contextlist><context>directory</context><context>.htaccess</context>
-</contextlist>
-<override>Limit</override>
-
-<usage>
-    <p>This directive allows access to the server to be restricted
-    based on hostname, IP address, or environment variables. The
-    arguments for the <directive>Deny</directive> directive are
-    identical to the arguments for the <directive
-    module="mod_access_compat">Allow</directive> directive.</p>
-</usage>
-</directivesynopsis>
-
-<directivesynopsis>
-<name>Order</name>
-<description>Controls the default access state and the order in which
-<directive>Allow</directive> and <directive>Deny</directive> are
-evaluated.</description>
-<syntax> Order <var>ordering</var></syntax>
-<default>Order Deny,Allow</default>
-<contextlist><context>directory</context><context>.htaccess</context>
-</contextlist>
-<override>Limit</override>
-
-<usage>
-    <p>The <directive>Order</directive> directive controls the default
-    access state and the order in which <directive
-    module="mod_access_compat">Allow</directive> and <directive
-    module="mod_access_compat">Deny</directive> directives are evaluated.
-    <var>Ordering</var> is one of</p>
-
-    <dl>
-      <dt><code>Deny,Allow</code></dt>
-
-      <dd>The <directive module="mod_access_compat">Deny</directive> directives
-      are evaluated before the <directive
-      module="mod_access_compat">Allow</directive> directives. Access is
-      allowed by default. Any client which does not match a
-      <directive module="mod_access_compat">Deny</directive> directive or does
-      match an <directive module="mod_access_compat">Allow</directive>
-      directive will be allowed access to the server.</dd>
-
-      <dt><code>Allow,Deny</code></dt>
-
-      <dd>The <directive module="mod_access_compat">Allow</directive>
-      directives are evaluated before the <directive
-      module="mod_access_compat">Deny</directive> directives. Access is denied
-      by default. Any client which does not match an <directive
-      module="mod_access_compat">Allow</directive> directive or does match a
-      <directive module="mod_access_compat">Deny</directive> directive will be
-      denied access to the server.</dd>
-
-      <dt><code>Mutual-failure</code></dt>
-
-      <dd>Only those hosts which appear on the <directive
-      module="mod_access_compat">Allow</directive> list and do not appear on
-      the <directive module="mod_access_compat">Deny</directive> list are
-      granted access. This ordering has the same effect as <code>Order
-      Allow,Deny</code> and is deprecated in favor of that
-      configuration.</dd>
-    </dl>
-
-    <p>Keywords may only be separated by a comma; <em>no whitespace</em> is
-    allowed between them. Note that in all cases every <directive
-    module="mod_access_compat">Allow</directive> and <directive
-    module="mod_access_compat">Deny</directive> statement is evaluated.</p>
-
-    <p>In the following example, all hosts in the apache.org domain
-    are allowed access; all other hosts are denied access.</p>
-
-    <example>
-      Order Deny,Allow<br />
-      Deny from all<br />
-      Allow from apache.org
-    </example>
-
-    <p>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.</p>
-
-    <example>
-      Order Allow,Deny<br />
-      Allow from apache.org<br />
-      Deny from foo.apache.org
-    </example>
-
-    <p>On the other hand, if the <directive>Order</directive> in the last
-    example is changed to <code>Deny,Allow</code>, all hosts will
-    be allowed access. This happens because, regardless of the
-    actual ordering of the directives in the configuration file,
-    the <code>Allow from apache.org</code> will be evaluated last
-    and will override the <code>Deny from foo.apache.org</code>.
-    All hosts not in the <code>apache.org</code> domain will also
-    be allowed access because the default state will change to
-    <em>allow</em>.</p>
-
-    <p>The presence of an <directive>Order</directive> directive can affect
-    access to a part of the server even in the absence of accompanying
-    <directive module="mod_access_compat">Allow</directive> and <directive
-    module="mod_access_compat">Deny</directive> directives because of its effect
-    on the default access state. For example,</p>
-
-    <example>
-      &lt;Directory /www&gt;<br />
-      <indent>
-        Order Allow,Deny<br />
-      </indent>
-      &lt;/Directory&gt;
-    </example>
-
-    <p>will deny all access to the <code>/www</code> directory
-    because the default access state will be set to
-    <em>deny</em>.</p>
-
-    <p>The <directive>Order</directive> directive controls the order of access
-    directive processing only within each phase of the server's
-    configuration processing. This implies, for example, that an
-    <directive module="mod_access_compat">Allow</directive> or <directive
-    module="mod_access_compat">Deny</directive> directive occurring in a
-    <directive module="core" type="section">Location</directive> section will
-    always be evaluated after an <directive
-    module="mod_access_compat">Allow</directive> or <directive
-    module="mod_access_compat">Deny</directive> directive occurring in a
-    <directive module="core" type="section">Directory</directive> section or
-    <code>.htaccess</code> file, regardless of the setting of the
-    <directive>Order</directive> directive. For details on the merging
-    of configuration sections, see the documentation on <a
-    href="../sections.html">How Directory, Location and Files sections
-    work</a>.</p>
-</usage>
-</directivesynopsis>
-
-<directivesynopsis>
-<name>Satisfy</name>
-<description>Interaction between host-level access control and
-user authentication</description>
-<syntax>Satisfy Any|All</syntax>
-<default>Satisfy All</default>
-<contextlist><context>directory</context><context>.htaccess</context>
-</contextlist>
-<override>AuthConfig</override>
-<compatibility>Influenced by <directive module="core" type="section"
->Limit</directive> and <directive module="core"
-type="section">LimitExcept</directive> in version 2.0.51 and
-later</compatibility>
-
-<usage>
-    <p>Access policy if both <directive
-    module="mod_authz_host">Allow</directive> and <directive
-    module="mod_authz_core">Require</directive> used. The parameter can be
-    either <code>All</code> or <code>Any</code>. This directive is only
-    useful if access to a particular area is being restricted by both
-    username/password <em>and</em> client host address. In this case
-    the default behavior (<code>All</code>) is to require that the client
-    passes the address access restriction <em>and</em> enters a valid
-    username and password. With the <code>Any</code> option the client will be
-    granted access if they either pass the host restriction or enter a
-    valid username and password. This can be used to password restrict
-    an area, but to let clients from particular addresses in without
-    prompting for a password.</p>
-
-    <p>For example, if you wanted to let people on your network have
-    unrestricted access to a portion of your website, but require that
-    people outside of your network provide a password, you could use a
-    configuration similar to the following:</p>
-
-    <example>
-      Require valid-user<br />
-      Allow from 192.168.1<br />
-      Satisfy Any
-    </example>
-
-    <p>Since version 2.0.51 <directive>Satisfy</directive> directives can
-    be restricted to particular methods by <directive module="core"
-    type="section">Limit</directive> and <directive module="core" type="section"
-    >LimitExcept</directive> sections.</p>
-</usage>
-   <seealso><directive module="mod_access_compat">Allow</directive></seealso>
-   <seealso><directive module="mod_authz_core">Require</directive></seealso>
-</directivesynopsis>
-
-</modulesynopsis>
+<?xml version="1.0"?>
+<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
+<?xml-stylesheet type="text/xsl" href="../style/manual.en.xsl"?>
+<!-- $LastChangedRevision$ -->
+
+<!--
+ Copyright 2002-2005 The Apache Software Foundation or its licensors, as
+ applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<modulesynopsis metafile="mod_access_compat.xml.meta">
+
+<name>mod_access_compat</name> 
+<description>Group authorizations based on host (name or IP
+address)</description>
+<status>Extension</status>
+<sourcefile>mod_access_compat.c</sourcefile>
+<identifier>access_compat_module</identifier>
+<compatibility>Available in Apache 2.3 as a compatibility module with 
+previous versions of Apache 2.x.  The directives provided by this module
+have been deprecated by the new authz refactoring.  Please see 
+<module>mod_authz_host</module></compatibility>
+
+<summary>
+    <p>The directives provided by <module>mod_access_compat</module> are
+    used in <directive module="core" type="section">Directory</directive>,
+    <directive module="core" type="section">Files</directive>, and
+    <directive module="core" type="section">Location</directive> sections
+    as well as <code><a href="core.html#accessfilename">.htaccess</a>
+    </code> files to control access to particular parts of the server.
+    Access can be controlled based on the client hostname, IP address, or
+    other characteristics of the client request, as captured in <a
+    href="../env.html">environment variables</a>. The <directive
+    module="mod_access_compat">Allow</directive> and <directive
+    module="mod_access_compat">Deny</directive> directives are used to
+    specify which clients are or are not allowed access to the server,
+    while the <directive module="mod_access_compat">Order</directive>
+    directive sets the default access state, and configures how the
+    <directive module="mod_access_compat">Allow</directive> and <directive
+    module="mod_access_compat">Deny</directive> directives interact with each
+    other.</p>
+
+    <p>Both host-based access restrictions and password-based
+    authentication may be implemented simultaneously. In that case,
+    the <directive module="core">Satisfy</directive> directive is used
+    to determine how the two sets of restrictions interact.</p>
+
+    <note type="warning"><title>Note</title>
+      <p>The directives provided by <module>mod_access_compat</module> have
+      been deprecated by the new authz refactoring. Please see 
+      <module>mod_authz_host</module>.  The module 
+      <module>mod_authz_default</module> must also be loaded to provide for
+      default authorization handling.</p>
+    </note>
+
+    <p>In general, access restriction directives apply to all
+    access methods (<code>GET</code>, <code>PUT</code>,
+    <code>POST</code>, 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 <directive module="core" type="section">Limit</directive> section.</p>
+</summary>
+
+<seealso><directive module="mod_authz_core">Require</directive></seealso>
+<seealso><module>mod_authz_host</module></seealso>
+<seealso><module>mod_authz_core</module></seealso>
+
+<directivesynopsis>
+<name>Allow</name>
+<description>Controls which hosts can access an area of the
+server</description>
+<syntax> Allow from all|<var>host</var>|env=<var>env-variable</var>
+[<var>host</var>|env=<var>env-variable</var>] ...</syntax>
+<contextlist><context>directory</context><context>.htaccess</context>
+</contextlist>
+<override>Limit</override>
+
+<usage>
+    <p>The <directive>Allow</directive> directive affects 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.</p>
+
+    <p>The first argument to this directive is always
+    <code>from</code>. The subsequent arguments can take three
+    different forms. If <code>Allow from all</code> is specified, then
+    all hosts are allowed access, subject to the configuration of the
+    <directive module="mod_access_compat">Deny</directive> and <directive
+    module="mod_access_compat">Order</directive> directives as discussed
+    below. To allow only particular hosts or groups of hosts to access
+    the server, the <em>host</em> can be specified in any of the
+    following formats:</p>
+
+    <dl>
+      <dt>A (partial) domain-name</dt>
+
+      <dd>
+      <example><title>Example:</title>
+        Allow from apache.org<br />
+        Allow from .net example.edu
+      </example>
+      <p>Hosts whose names match, or end in, this string are allowed
+      access. Only complete components are matched, so the above
+      example will match <code>foo.apache.org</code> but it will not
+      match <code>fooapache.org</code>. This configuration will cause
+      Apache to perform a double reverse DNS lookup on the client IP
+      address, regardless of the setting of the <directive
+      module="core">HostnameLookups</directive> 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.</p></dd>
+
+      <dt>A full IP address</dt>
+
+      <dd>
+      <example><title>Example:</title>
+        Allow from 10.1.2.3<br />
+        Allow from 192.168.1.104 192.168.1.205
+      </example>
+      <p>An IP address of a host allowed access</p></dd>
+
+      <dt>A partial IP address</dt>
+
+      <dd>
+      <example><title>Example:</title>
+        Allow from 10.1<br />
+        Allow from 10 172.20 192.168.2
+      </example>
+      <p>The first 1 to 3 bytes of an IP address, for subnet
+      restriction.</p></dd>
+
+      <dt>A network/netmask pair</dt>
+
+      <dd>
+      <example><title>Example:</title>
+        Allow from 10.1.0.0/255.255.0.0
+      </example>
+      <p>A network a.b.c.d, and a netmask w.x.y.z. For more
+      fine-grained subnet restriction.</p></dd>
+
+      <dt>A network/nnn CIDR specification</dt>
+
+      <dd>
+      <example><title>Example:</title>
+        Allow from 10.1.0.0/16
+      </example>
+      <p>Similar to the previous case, except the netmask consists of
+      nnn high-order 1 bits.</p></dd>
+    </dl>
+
+    <p>Note that the last three examples above match exactly the
+    same set of hosts.</p>
+
+    <p>IPv6 addresses and IPv6 subnets can be specified as shown
+    below:</p>
+
+    <example>
+       Allow from 2001:db8::a00:20ff:fea7:ccea<br />
+       Allow from 2001:db8::a00:20ff:fea7:ccea/10
+    </example>
+
+    <p>The third format of the arguments to the
+    <directive>Allow</directive> directive allows access to the server
+    to be controlled based on the existence of an <a
+    href="../env.html">environment variable</a>. When <code>Allow from
+    env=<var>env-variable</var></code> is specified, then the request is
+    allowed access if the environment variable <var>env-variable</var>
+    exists. The server provides the ability to set environment
+    variables in a flexible way based on characteristics of the client
+    request using the directives provided by
+    <module>mod_setenvif</module>. Therefore, this directive can be
+    used to allow access based on such factors as the clients
+    <code>User-Agent</code> (browser type), <code>Referer</code>, or
+    other HTTP request header fields.</p>
+
+    <example><title>Example:</title>
+      SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in<br />
+      &lt;Directory /docroot&gt;<br />
+      <indent>
+        Order Deny,Allow<br />
+        Deny from all<br />
+        Allow from env=let_me_in<br />
+      </indent>
+      &lt;/Directory&gt;
+    </example>
+
+    <p>In this case, browsers with a user-agent string beginning
+    with <code>KnockKnock/2.0</code> will be allowed access, and all
+    others will be denied.</p>
+</usage>
+</directivesynopsis>
+
+<directivesynopsis>
+<name>Deny</name>
+<description>Controls which hosts are denied access to the
+server</description>
+<syntax> Deny from all|<var>host</var>|env=<var>env-variable</var>
+[<var>host</var>|env=<var>env-variable</var>] ...</syntax>
+<contextlist><context>directory</context><context>.htaccess</context>
+</contextlist>
+<override>Limit</override>
+
+<usage>
+    <p>This directive allows access to the server to be restricted
+    based on hostname, IP address, or environment variables. The
+    arguments for the <directive>Deny</directive> directive are
+    identical to the arguments for the <directive
+    module="mod_access_compat">Allow</directive> directive.</p>
+</usage>
+</directivesynopsis>
+
+<directivesynopsis>
+<name>Order</name>
+<description>Controls the default access state and the order in which
+<directive>Allow</directive> and <directive>Deny</directive> are
+evaluated.</description>
+<syntax> Order <var>ordering</var></syntax>
+<default>Order Deny,Allow</default>
+<contextlist><context>directory</context><context>.htaccess</context>
+</contextlist>
+<override>Limit</override>
+
+<usage>
+    <p>The <directive>Order</directive> directive controls the default
+    access state and the order in which <directive
+    module="mod_access_compat">Allow</directive> and <directive
+    module="mod_access_compat">Deny</directive> directives are evaluated.
+    <var>Ordering</var> is one of</p>
+
+    <dl>
+      <dt><code>Deny,Allow</code></dt>
+
+      <dd>The <directive module="mod_access_compat">Deny</directive> directives
+      are evaluated before the <directive
+      module="mod_access_compat">Allow</directive> directives. Access is
+      allowed by default. Any client which does not match a
+      <directive module="mod_access_compat">Deny</directive> directive or does
+      match an <directive module="mod_access_compat">Allow</directive>
+      directive will be allowed access to the server.</dd>
+
+      <dt><code>Allow,Deny</code></dt>
+
+      <dd>The <directive module="mod_access_compat">Allow</directive>
+      directives are evaluated before the <directive
+      module="mod_access_compat">Deny</directive> directives. Access is denied
+      by default. Any client which does not match an <directive
+      module="mod_access_compat">Allow</directive> directive or does match a
+      <directive module="mod_access_compat">Deny</directive> directive will be
+      denied access to the server.</dd>
+
+      <dt><code>Mutual-failure</code></dt>
+
+      <dd>Only those hosts which appear on the <directive
+      module="mod_access_compat">Allow</directive> list and do not appear on
+      the <directive module="mod_access_compat">Deny</directive> list are
+      granted access. This ordering has the same effect as <code>Order
+      Allow,Deny</code> and is deprecated in favor of that
+      configuration.</dd>
+    </dl>
+
+    <p>Keywords may only be separated by a comma; <em>no whitespace</em> is
+    allowed between them. Note that in all cases every <directive
+    module="mod_access_compat">Allow</directive> and <directive
+    module="mod_access_compat">Deny</directive> statement is evaluated.</p>
+
+    <p>In the following example, all hosts in the apache.org domain
+    are allowed access; all other hosts are denied access.</p>
+
+    <example>
+      Order Deny,Allow<br />
+      Deny from all<br />
+      Allow from apache.org
+    </example>
+
+    <p>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.</p>
+
+    <example>
+      Order Allow,Deny<br />
+      Allow from apache.org<br />
+      Deny from foo.apache.org
+    </example>
+
+    <p>On the other hand, if the <directive>Order</directive> in the last
+    example is changed to <code>Deny,Allow</code>, all hosts will
+    be allowed access. This happens because, regardless of the
+    actual ordering of the directives in the configuration file,
+    the <code>Allow from apache.org</code> will be evaluated last
+    and will override the <code>Deny from foo.apache.org</code>.
+    All hosts not in the <code>apache.org</code> domain will also
+    be allowed access because the default state will change to
+    <em>allow</em>.</p>
+
+    <p>The presence of an <directive>Order</directive> directive can affect
+    access to a part of the server even in the absence of accompanying
+    <directive module="mod_access_compat">Allow</directive> and <directive
+    module="mod_access_compat">Deny</directive> directives because of its effect
+    on the default access state. For example,</p>
+
+    <example>
+      &lt;Directory /www&gt;<br />
+      <indent>
+        Order Allow,Deny<br />
+      </indent>
+      &lt;/Directory&gt;
+    </example>
+
+    <p>will deny all access to the <code>/www</code> directory
+    because the default access state will be set to
+    <em>deny</em>.</p>
+
+    <p>The <directive>Order</directive> directive controls the order of access
+    directive processing only within each phase of the server's
+    configuration processing. This implies, for example, that an
+    <directive module="mod_access_compat">Allow</directive> or <directive
+    module="mod_access_compat">Deny</directive> directive occurring in a
+    <directive module="core" type="section">Location</directive> section will
+    always be evaluated after an <directive
+    module="mod_access_compat">Allow</directive> or <directive
+    module="mod_access_compat">Deny</directive> directive occurring in a
+    <directive module="core" type="section">Directory</directive> section or
+    <code>.htaccess</code> file, regardless of the setting of the
+    <directive>Order</directive> directive. For details on the merging
+    of configuration sections, see the documentation on <a
+    href="../sections.html">How Directory, Location and Files sections
+    work</a>.</p>
+</usage>
+</directivesynopsis>
+
+<directivesynopsis>
+<name>Satisfy</name>
+<description>Interaction between host-level access control and
+user authentication</description>
+<syntax>Satisfy Any|All</syntax>
+<default>Satisfy All</default>
+<contextlist><context>directory</context><context>.htaccess</context>
+</contextlist>
+<override>AuthConfig</override>
+<compatibility>Influenced by <directive module="core" type="section"
+>Limit</directive> and <directive module="core"
+type="section">LimitExcept</directive> in version 2.0.51 and
+later</compatibility>
+
+<usage>
+    <p>Access policy if both <directive
+    module="mod_authz_host">Allow</directive> and <directive
+    module="mod_authz_core">Require</directive> used. The parameter can be
+    either <code>All</code> or <code>Any</code>. This directive is only
+    useful if access to a particular area is being restricted by both
+    username/password <em>and</em> client host address. In this case
+    the default behavior (<code>All</code>) is to require that the client
+    passes the address access restriction <em>and</em> enters a valid
+    username and password. With the <code>Any</code> option the client will be
+    granted access if they either pass the host restriction or enter a
+    valid username and password. This can be used to password restrict
+    an area, but to let clients from particular addresses in without
+    prompting for a password.</p>
+
+    <p>For example, if you wanted to let people on your network have
+    unrestricted access to a portion of your website, but require that
+    people outside of your network provide a password, you could use a
+    configuration similar to the following:</p>
+
+    <example>
+      Require valid-user<br />
+      Allow from 192.168.1<br />
+      Satisfy Any
+    </example>
+
+    <p>Since version 2.0.51 <directive>Satisfy</directive> directives can
+    be restricted to particular methods by <directive module="core"
+    type="section">Limit</directive> and <directive module="core" type="section"
+    >LimitExcept</directive> sections.</p>
+</usage>
+   <seealso><directive module="mod_access_compat">Allow</directive></seealso>
+   <seealso><directive module="mod_authz_core">Require</directive></seealso>
+</directivesynopsis>
+
+</modulesynopsis>

Propchange: httpd/httpd/trunk/docs/manual/mod/mod_access_compat.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: httpd/httpd/trunk/docs/manual/mod/mod_access_compat.xml
------------------------------------------------------------------------------
    svn:keywords = LastChangedRevision

Modified: httpd/httpd/trunk/docs/manual/mod/mod_dav.html.ja.euc-jp
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/mod_dav.html.ja.euc-jp?rev=375322&r1=375321&r2=375322&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_dav.html.ja.euc-jp [euc-jp] (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_dav.html.ja.euc-jp [euc-jp] Mon Feb  6 09:55:59 2006
@@ -26,6 +26,8 @@
 <a href="../ja/mod/mod_dav.html" title="Japanese">&nbsp;ja&nbsp;</a> |
 <a href="../ko/mod/mod_dav.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a></p>
 </div>
+<div class="outofdate">This translation may be out of date. Check the
+            English version for recent changes.</div>
 <table class="module"><tr><th><a href="module-dict.html#Description">説明:</a></th><td>分散オーサリングとバージョン管理
 (<a href="http://www.webdav.org/">WebDAV</a>) 機能</td></tr>
 <tr><th><a href="module-dict.html#Status">ステータス:</a></th><td>Extension</td></tr>



Mime
View raw message