cvs commit: httpd-docs-1.3/htdocs/manual/mod mod_auth.html

[coar]

coar        01/09/10 10:51:31

  Modified:    htdocs/manual/mod mod_auth.html
  Log:
  Foo, I said see the docco for an example and then didn't include one..
  
  Revision  Changes    Path
  1.26      +24 -0     httpd-docs-1.3/htdocs/manual/mod/mod_auth.html
  
  Index: mod_auth.html
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/mod/mod_auth.html,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -u -r1.25 -r1.26
  --- mod_auth.html     2001/09/10 17:14:51     1.25
  +++ mod_auth.html     2001/09/10 17:51:31     1.26
  @@ -106,6 +106,30 @@
   
   <hr>
   
  +<h2><a name="example">Example of <code>Require file-owner</code></a></h2>
  +<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 AuthUserFile database that lists all
  +of their usernames, and that their Web usernames match the ones 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>
  +<pre>
  +    &lt;Directory /home/*/public_html/private&gt;
  +        AuthType Basic
  +        AuthName MyPrivateFile
  +        AuthUserFile /usr/local/apache/etc/.htpasswd-allusers
  +        Satisfy All
  +        Require file-owner
  +    &lt;/Directory&gt;
  +</pre>
  +
  +<hr>
  +
   <H2><A NAME="authgroupfile">AuthGroupFile</A> directive</H2>
   <!--%plaintext &lt;?INDEX {\tt AuthGroupFile} directive&gt; -->
   <A
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]