⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 mod_authz_owner.html.en

📁 Apache官方在今天放出产品系列2.2的最新版本2.2.11的源码包 最流行的HTTP服务器软件之一
💻 EN
字号:
<?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_authz_owner - 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.2</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.2</a> &gt; <a href="./">Modules</a></div><div id="page-content"><div id="preamble"><h1>Apache Module mod_authz_owner</h1><div class="toplang"><p><span>Available Languages: </span><a href="../en/mod/mod_authz_owner.html" title="English">&nbsp;en&nbsp;</a> |<a href="../ja/mod/mod_authz_owner.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |<a href="../ko/mod/mod_authz_owner.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a></p></div><table class="module"><tr><th><a href="module-dict.html#Description">Description:</a></th><td>Authorization based on file ownership</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營dentifier:</a></th><td>authz_owner_module</td></tr><tr><th><a href="module-dict.html#SourceFile">Source燜ile:</a></th><td>mod_authz_owner.c</td></tr><tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache 2.1 and later</td></tr></table><h3>Summary</h3>    <p>This module authorizes access to files by comparing the userid used    for HTTP authentication (the web userid) with the file-system owner or    group of the requested file. The supplied username and password    must be already properly verified by an authentication module,    such as <code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code> or    <code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code>. <code class="module"><a href="../mod/mod_authz_owner.html">mod_authz_owner</a></code>    recognizes two arguments for the <code class="directive"><a href="../mod/core.html#require">Require</a></code> directive, <code>file-owner</code> and    <code>file-group</code>, as follows:</p>    <dl>      <dt><code>file-owner</code></dt>      <dd>The supplied web-username must match the system's name for the      owner of the file being requested. That is, if the operating system      says the requested file is owned by <code>jones</code>, then the      username used to access it through the web must be <code>jones</code>      as well.</dd>      <dt><code>file-group</code></dt>      <dd>The name of the system group that owns the file must be present      in a group database, which is provided, for example, by <code class="module"><a href="../mod/mod_authz_groupfile.html">mod_authz_groupfile</a></code> or <code class="module"><a href="../mod/mod_authz_dbm.html">mod_authz_dbm</a></code>,      and the web-username must be a member of that group. For example, if      the operating system says the requested file is owned by (system)      group <code>accounts</code>, the group <code>accounts</code> must      appear in the group database and the web-username used in the request      must be a member of that group.</dd>    </dl>    <div class="note"><h3>Note</h3>      <p>If <code class="module"><a href="../mod/mod_authz_owner.html">mod_authz_owner</a></code> is used in order to authorize      a resource that is not actually present in the filesystem      (<em>i.e.</em> a virtual resource), it will deny the access.</p>      <p>Particularly it will never authorize <a href="../content-negotiation.html#multiviews">content negotiated      "MultiViews"</a> resources.</p>    </div></div><div id="quickview"><h3 class="directives">Directives</h3><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#authzownerauthoritative">AuthzOwnerAuthoritative</a></li></ul><h3>Topics</h3><ul id="topics"><li><img alt="" src="../images/down.gif" /> <a href="#examples">Configuration Examples</a></li></ul><h3>See also</h3><ul class="seealso"><li><code class="directive"><a href="../mod/core.html#require">Require</a></code></li><li><code class="directive"><a href="../mod/core.html#satisfy">Satisfy</a></code></li></ul></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="examples" id="examples">Configuration Examples</a></h2>    <h3><a name="examples.file-owner" id="examples.file-owner">Require file-owner</a></h3>      <p>Consider a multi-user system running the Apache Web server, with      each user having his or her own files in <code>~/public_html/private</code>. Assuming that there is a single      <code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmuserfile">AuthDBMUserFile</a></code> database      that lists all of their web-usernames, and that these usernames match      the system's usernames that actually own the files on the server, then      the following stanza would allow only the user himself access to his      own files. User <code>jones</code> would not be allowed to access      files in <code>/home/smith/public_html/private</code> unless they      were owned by <code>jones</code> instead of <code>smith</code>.</p>      <div class="example"><p><code>        &lt;Directory /home/*/public_html/private&gt;<br />        <span class="indent">          AuthType Basic<br />          AuthName MyPrivateFiles<br />          AuthBasicProvider dbm<br />          AuthDBMUserFile /usr/local/apache2/etc/.htdbm-all<br />          Satisfy All<br />          Require file-owner<br />        </span>        &lt;/Directory&gt;      </code></p></div>        <h3><a name="examples.file-group" id="examples.file-group">Require file-group</a></h3>      <p>Consider a system similar to the one described above, but with      some users that share their project files in      <code>~/public_html/project-foo</code>. The files are owned by the      system group <code>foo</code> and there is a single <code class="directive"><a href="../mod/mod_authz_dbm.html#authdbmgroupfile">AuthDBMGroupFile</a></code> database that      contains all of the web-usernames and their group membership,      <em>i.e.</em> they must be at least member of a group named      <code>foo</code>. So if <code>jones</code> and <code>smith</code>      are both member of the group <code>foo</code>, then both will be      authorized to access the <code>project-foo</code> directories of      each other.</p>      <div class="example"><p><code>        &lt;Directory /home/*/public_html/project-foo&gt;<br />        <span class="indent">          AuthType Basic<br />          AuthName "Project Foo Files"<br />          AuthBasicProvider dbm<br />          <br />          # combined user/group database<br />          AuthDBMUserFile  /usr/local/apache2/etc/.htdbm-all<br />          AuthDBMGroupFile /usr/local/apache2/etc/.htdbm-all<br />          <br />          Satisfy All<br />          Require file-group<br />        </span>        &lt;/Directory&gt;      </code></p></div>    </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="directive-section"><h2><a name="AuthzOwnerAuthoritative" id="AuthzOwnerAuthoritative">AuthzOwnerAuthoritative</a> <a name="authzownerauthoritative" id="authzownerauthoritative">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Sets whether authorization will be passed on to lower levelmodules</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>AuthzOwnerAuthoritative On|Off</code></td></tr><tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>AuthzOwnerAuthoritative On</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_authz_owner</td></tr></table>    <p>Setting the <code class="directive">AuthzOwnerAuthoritative</code>    directive explicitly to <code>Off</code> allows for    user authorization to be passed on to lower level modules (as defined    in the <code>modules.c</code> files) if:</p>    <ul>    <li>in the case of <code>file-owner</code> the file-system owner does not    match the supplied web-username or could not be determined, or</li>    <li>in the case of <code>file-group</code> the file-system group does not    contain the supplied web-username or could not be determined.</li>    </ul>    <p>Note that setting the value to <code>Off</code> also allows the    combination of <code>file-owner</code> and <code>file-group</code>, so    access will be allowed if either one or the other (or both) match.</p>    <p>By default, control is not passed on and an authorization failure    will result in an "Authentication Required" reply. Not    setting it to <code>Off</code> thus keeps the system secure and forces    an NCSA compliant behaviour.</p></div></div><div class="bottomlang"><p><span>Available Languages: </span><a href="../en/mod/mod_authz_owner.html" title="English">&nbsp;en&nbsp;</a> |<a href="../ja/mod/mod_authz_owner.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |<a href="../ko/mod/mod_authz_owner.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a></p></div><div id="footer"><p class="apache">Copyright 2008 The Apache Software Foundation.<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>

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -