Forum Moderators: phranque
#
# UserDir: The name of the directory that is appended onto a user's home
# directory if a ~user request is received. Be especially careful to use
# proper, forward slashes here. On Windows NT, "Personal/My Website"
# is a more appropriate choice.
#
UserDir "My Documents/My Website"
#
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
#
# You must correct the path for the root to match your system's configured
# user directory location, e.g. "C:/WinNT/profiles/*/My Documents/My Website"
# or whichever, as appropriate.
#
#<Directory "C:/Documents and Settings/*/My Documents/My Website">
# AllowOverride FileInfo AuthConfig Limit
# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
# <Limit GET POST OPTIONS PROPFIND>
# Order allow,deny
# Allow from all
# </Limit>
# <LimitExcept GET POST OPTIONS PROPFIND>
# Order deny,allow
# Deny from all
# </LimitExcept>
#</Directory>
C:/Documents and Settings/
So, let's say Userdir is set to "My Documents/My Website" as in your example. If you request a web page at http://www.example.com/~ashishjha, it will serve up this page:
C:/Documents and Settings/ashishjha/My Documents/My Website/index.htm
So, in other words, all of the web pages for 'ashishjha' are in "C:/Documents and Settings/ashishjha/My Documents/My Website"
Many web sites don't use this feature at all (and thus have Userdir commented out). It works well if you have a server that multiple people are using. Each person effectively has their own little "web site", using a URL like "http://www.example.com/~username". And that user's content is completely separate from the main site found at http://www.example.com/