From: Rich Bowen Date: Mon, 18 Feb 2002 03:41:05 +0000 (+0000) Subject: Conversion to XML. X-Git-Tag: 2.0.33~216 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=bedf532d6d8663c5eb80c2d26dab052ea3d6269c;p=apache Conversion to XML. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93469 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_userdir.xml b/docs/manual/mod/mod_userdir.xml new file mode 100755 index 0000000000..65777a7e45 --- /dev/null +++ b/docs/manual/mod/mod_userdir.xml @@ -0,0 +1,107 @@ + + + + +mod_userdir +Base +This module provides for user-specific +directories. +userdir_module +mod_userdir.c + + + + + + + +UserDir +Sets the directory from which to serve files when requests +for a particular user are received, denoted by requests containing +~username, such as +http://server.example.com/~bob/ +UserDir directory-filename +UserDir public_html +server config virtual +host +All forms except the UserDir public_html +form are only available in Apache 1.1 or above. Use of the +enabled keyword, or disabled with a +list of usernames, is only available in Apache 1.3 and +above. + + + +

The UserDir directive sets the real directory in a user's + home directory to use when a request for a document for a user + is received. Directory-filename is one of the + following:

+ +
    +
  • The name of a directory or a pattern such as those shown + below.
  • + +
  • The keyword disabled. This turns off + all username-to-directory translations except those + explicitly named with the enabled keyword (see + below).
  • + +
  • The keyword disabled followed by a + space-delimited list of usernames. Usernames that appear in + such a list will never have directory translation + performed, even if they appear in an enabled + clause.
  • + +
  • The keyword enabled followed by a + space-delimited list of usernames. These usernames will have + directory translation performed even if a global disable is + in effect, but not if they also appear in a + disabled clause.
  • +
+ +

If neither the enabled nor the + disabled keywords appear in the + Userdir directive, the argument is treated as a + filename pattern, and is used to turn the name into a directory + specification. A request for + http://www.foo.com/~bob/one/two.html will be + translated to:

+ + + + + + + +
UserDir directive usedTranslated path
UserDir public_html~bob/public_html/one/two.html
UserDir /usr/web/usr/web/bob/one/two.html
UserDir /home/*/www/home/bob/www/one/two.html
+ +

The following directives will send redirects to the client:

+ + + + + + + +
UserDir directive usedTranslated path
UserDir http://www.foo.com/usershttp://www.foo.com/users/bob/one/two.html
UserDir +http://www.foo.com/*/usrhttp://www.foo.com/bob/usr/one/two.html
UserDir +http://www.foo.com/~*/http://www.foo.com/~bob/one/two.html
+ +
+ Be careful when using this directive; for instance, + "UserDir ./" would map + "/~root" to "/" - which is probably + undesirable. If you are running Apache 1.3 or above, it is + strongly recommended that your configuration include a + "UserDir disabled root" declaration. + See also the Directory + directive and the Security + Tips page for more information. +
+ +
+ +
+
+ +