mirror of
				https://github.com/apache/httpd.git
				synced 2025-11-03 17:53:20 +03:00 
			
		
		
		
	Trim trailing whitespace... no func change git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1174747 13f79535-47bb-0310-9956-ffa450edef68
		
			
				
	
	
		
			199 lines
		
	
	
		
			7.0 KiB
		
	
	
	
		
			XML
		
	
	
	
	
	
			
		
		
	
	
			199 lines
		
	
	
		
			7.0 KiB
		
	
	
	
		
			XML
		
	
	
	
	
	
<?xml version='1.0' encoding='UTF-8' ?>
 | 
						|
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
 | 
						|
<?xml-stylesheet type="text/xsl" href="../style/manual.en.xsl"?>
 | 
						|
<!-- $LastChangedRevision$ -->
 | 
						|
 | 
						|
<!--
 | 
						|
 Licensed to the Apache Software Foundation (ASF) under one or more
 | 
						|
 contributor license agreements.  See the NOTICE file distributed with
 | 
						|
 this work for additional information regarding copyright ownership.
 | 
						|
 The ASF licenses this file to You 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.
 | 
						|
-->
 | 
						|
 | 
						|
<manualpage metafile="public_html.xml.meta">
 | 
						|
<parentdocument href="./">How-To / Tutorials</parentdocument>
 | 
						|
 | 
						|
  <title>Per-user web directories</title>
 | 
						|
 | 
						|
<summary>
 | 
						|
<p>On systems with multiple users, each user can be permitted to have a
 | 
						|
    web site in their home directory using the <directive
 | 
						|
    module="mod_userdir">UserDir</directive> directive. Visitors
 | 
						|
    to a URL <code>http://example.com/~username/</code> will get content
 | 
						|
    out of the home directory of the user "<code>username</code>", out of
 | 
						|
    the subdirectory specified by the <directive
 | 
						|
    module="mod_userdir">UserDir</directive> directive.</p>
 | 
						|
<p>Note that, by default, access to these directories is <strong>not</strong>
 | 
						|
    enabled. You can enable access when using <directive module="mod_userdir"
 | 
						|
    >UserDir</directive> by uncommenting the line</p>
 | 
						|
    <example>
 | 
						|
      #Include conf/extra/httpd-userdir.conf
 | 
						|
    </example>
 | 
						|
    <p>in the default config file, and adapting the <code
 | 
						|
    >httpd-userdir.conf</code>
 | 
						|
    file as necessary, or by including the appropriate directives in a
 | 
						|
    <code>Directory</code> block within the main config file.</p>
 | 
						|
</summary>
 | 
						|
 | 
						|
<seealso><a href="../urlmapping.html">Mapping URLs to the Filesystem</a></seealso>
 | 
						|
 | 
						|
  <section id="related">
 | 
						|
    <title>Per-user web directories</title>
 | 
						|
    <related>
 | 
						|
      <modulelist>
 | 
						|
        <module>mod_userdir</module>
 | 
						|
      </modulelist>
 | 
						|
      <directivelist>
 | 
						|
        <directive module="mod_userdir">UserDir</directive>
 | 
						|
        <directive module="core">DirectoryMatch</directive>
 | 
						|
        <directive module="core">AllowOverride</directive>
 | 
						|
      </directivelist>
 | 
						|
    </related>
 | 
						|
    </section>
 | 
						|
 | 
						|
    <section id="userdir">
 | 
						|
    <title>Setting the file path with UserDir</title>
 | 
						|
 | 
						|
    <p>The <directive module="mod_userdir">UserDir</directive>
 | 
						|
    directive specifies a directory out of which per-user
 | 
						|
    content is loaded. This directive may take several different forms.</p>
 | 
						|
 | 
						|
    <p>If a path is given which does not start with a leading slash, it is
 | 
						|
    assumed to be a directory path relative to the home directory of the
 | 
						|
    specified user. Given this configuration:</p>
 | 
						|
 | 
						|
    <example>
 | 
						|
      UserDir public_html
 | 
						|
    </example>
 | 
						|
 | 
						|
    <p>the URL <code>http://example.com/~rbowen/file.html</code> will be
 | 
						|
    translated to the file path
 | 
						|
    <code>/home/rbowen/public_html/file.html</code></p>
 | 
						|
 | 
						|
    <p>If a path is given starting with a slash, a directory path will be
 | 
						|
    constructed using that path, plus the username specified. Given this
 | 
						|
    configuration:</p>
 | 
						|
 | 
						|
    <example>
 | 
						|
      UserDir /var/html
 | 
						|
    </example>
 | 
						|
 | 
						|
    <p>the URL <code>http://example.com/~rbowen/file.html</code> will be
 | 
						|
    translated to the file path <code>/var/html/rbowen/file.html</code></p>
 | 
						|
 | 
						|
    <p>If a path is provided which contains an asterisk (*), a path is used
 | 
						|
    in which the asterisk is replaced with the username. Given this
 | 
						|
    configuration:</p>
 | 
						|
 | 
						|
    <example>
 | 
						|
      UserDir /var/www/*/docs
 | 
						|
    </example>
 | 
						|
 | 
						|
    <p>the URL <code>http://example.com/~rbowen/file.html</code> will be
 | 
						|
    translated to the file path
 | 
						|
    <code>/var/www/rbowen/docs/file.html</code></p>
 | 
						|
 | 
						|
    <p>Multiple directories or directory paths can also be set.</p>
 | 
						|
 | 
						|
    <example>
 | 
						|
      UserDir public_html /var/html
 | 
						|
    </example>
 | 
						|
 | 
						|
    <p>For the URL <code>http://example.com/~rbowen/file.html</code>,
 | 
						|
    Apache will search for <code>~rbowen</code>. If it isn't found,
 | 
						|
    Apache will search for <code>rbowen</code> in <code>/var/html</code>. If
 | 
						|
    found, the above URL will then be translated to the file path
 | 
						|
    <code>/var/html/rbowen/file.html</code></p>
 | 
						|
 | 
						|
  </section>
 | 
						|
 | 
						|
  <section id="redirect">
 | 
						|
    <title>Redirecting to external URLs</title>
 | 
						|
    <p>The <directive module="mod_userdir">UserDir</directive> directive can be
 | 
						|
      used to redirect user directory requests to external URLs.</p>
 | 
						|
 | 
						|
    <example>
 | 
						|
      UserDir http://example.org/users/*/
 | 
						|
    </example>
 | 
						|
 | 
						|
    <p>The above example will redirect a request for
 | 
						|
    <code>http://example.com/~bob/abc.html</code> to
 | 
						|
    <code>http://example.org/users/bob/abc.html</code>.</p>
 | 
						|
  </section>
 | 
						|
 | 
						|
  <section id="enable">
 | 
						|
    <title>Restricting what users are permitted to use this
 | 
						|
    feature</title>
 | 
						|
 | 
						|
    <p>Using the syntax shown in the UserDir documentation, you can restrict
 | 
						|
    what users are permitted to use this functionality:</p>
 | 
						|
 | 
						|
    <example>
 | 
						|
      UserDir disabled root jro fish
 | 
						|
    </example>
 | 
						|
 | 
						|
    <p>The configuration above will enable the feature for all users
 | 
						|
    except for those listed in the <code>disabled</code> statement.
 | 
						|
    You can, likewise, disable the feature for all but a few users by
 | 
						|
    using a configuration like the following:</p>
 | 
						|
 | 
						|
    <example>
 | 
						|
      UserDir disabled<br />
 | 
						|
      UserDir enabled rbowen krietz
 | 
						|
    </example>
 | 
						|
 | 
						|
    <p>See <directive module="mod_userdir">UserDir</directive>
 | 
						|
    documentation for additional examples.</p>
 | 
						|
 | 
						|
  </section>
 | 
						|
 | 
						|
  <section id="cgi">
 | 
						|
  <title>Enabling a cgi directory for each user</title>
 | 
						|
 | 
						|
   <p>In order to give each user their own cgi-bin directory, you can use
 | 
						|
    a <directive module="core" type="section">Directory</directive>
 | 
						|
    directive to make a particular subdirectory of a user's home directory
 | 
						|
    cgi-enabled.</p>
 | 
						|
 | 
						|
    <example>
 | 
						|
      <Directory /home/*/public_html/cgi-bin/><br />
 | 
						|
       Options ExecCGI<br />
 | 
						|
       SetHandler cgi-script<br />
 | 
						|
       </Directory>
 | 
						|
    </example>
 | 
						|
 | 
						|
    <p>Then, presuming that <code>UserDir</code> is set to
 | 
						|
    <code>public_html</code>, a cgi program <code>example.cgi</code>
 | 
						|
    could be loaded from that directory as:</p>
 | 
						|
 | 
						|
    <example>
 | 
						|
    http://example.com/~rbowen/cgi-bin/example.cgi
 | 
						|
    </example>
 | 
						|
 | 
						|
    </section>
 | 
						|
 | 
						|
    <section id="htaccess">
 | 
						|
    <title>Allowing users to alter configuration</title>
 | 
						|
 | 
						|
    <p>If you want to allows users to modify the server configuration in
 | 
						|
    their web space, they will need to use <code>.htaccess</code> files to
 | 
						|
    make these changed. Ensure that you have set <directive
 | 
						|
    module="core">AllowOverride</directive> to a
 | 
						|
    value sufficient for the directives that you want to permit the users
 | 
						|
    to modify. See the <a href="htaccess.html">.htaccess tutorial</a> for
 | 
						|
    additional details on how this works.</p>
 | 
						|
 | 
						|
  </section>
 | 
						|
 | 
						|
</manualpage>
 |