paul 96/11/17 12:27:11
Modified: docs index.html mod_imap.html mod_userdir.html
Added: docs bind.html handler.html host.html keepalive.html
location.html mod_actions.html mod_auth_anon.html
mod_auth_db.html mod_auth_msql.html
mod_cern_meta.html mod_digest.html mod_env.html
mod_info.html mod_proxy.html mod_status.html
Log:
Update to 1.1 docs.
Revision Changes Path
1.2 +196 -41 apache/docs/index.html
Index: index.html
===================================================================
RCS file: /export/home/cvs/apache/docs/index.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** index.html 1996/11/17 20:22:42 1.1
--- index.html 1996/11/17 20:27:01 1.2
***************
*** 1,53 ****
! <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
! <HTML>
! <HEAD>
! <TITLE>Apache documentation</TITLE>
! </HEAD>
!
! <BODY>
! <IMG SRC="../images/apache_sub.gif" ALT="">
! <h1>Apache documentation</h1>
!
! <h2>Apache Users' Guide</h2>
! The Apache <A HREF="FAQ.html">Frequently Asked Questions</A> list.<p>
! <A HREF="known_bugs.html">Known Bugs</A> and
! <A href="compat_notes.html">compatibility notes</A> for Apache 0.8, with
! links to some of the <A HREF="features.html">new features</A>. <p>
!
! <h3>User guides for specific features</h3>
! <menu>
! <LI><A HREF="content-negotiation.html"> Content Negotiation</A>
! <LI><A HREF="custom-error.html">Custom Error Reponses</A>
! <li><A HREF="auth_dbm.html"> Faster User Authentication Lookups Using DBM
! Files</A>
! <LI><A HREF="process-model.html"> Minimal-forking process model</A>
! <LI><A HREF="virtual-host.html"> Virtual Hosts (multi-home)</A>
! </menu>
- <h3>Other notes</h3>
<ul>
! <li><A href="howto.html">How do I? documentation</A><p>
! <LI><A HREF="security_tips.html">Security tips</A>
! <LI><A HREF="perf.html">Performance hints</a> for heavily loaded web
servers.
</ul>
<hr>
! <H2>Apache Reference Manual</h2>
<ul>
! <li><A HREF="install.html">Compiling and Installing Apache</A><p>
! <li><A HREF="invoking.html">Starting Apache</A><p>
! <li><A HREF="directives.html">Apache run-time configuration
directives</A><p>
! <li><A HREF="modules.html">Apache modules</A><p>
! <li><A HREF="magic_types.html">Magic mime-types provided by Apache</A><p>
! <LI><A HREF="API.html">Highly generalized API to server functionality</A><p>
</ul>
- The Manual is also available in <A HREF="manual.ps.gz">gzipped
postscript</A>
- and a <A HREF="manual.tar.gz">LaTeX/Postscript tar file</A>.
- <P>
! <HR>
- <A HREF="../"><IMG SRC="../images/apache_home.gif" ALT="Home"></A>
</BODY>
</HTML>
--- 1,208 ----
! <html><head>
! <title>New features with Apache 1.1</title>
! </head><body>
!
! <img src="../../images/apache_sub.gif" alt="">
! <h1>Overview of new features</h1>
!
! <h2>API Changes</h2>
!
! A few changes to the Apache API were made for 1.1. It is possible
! that some third-party modules will no longer work with 1.1, though
! we have made every effort to provide backwards-compatibility. If you
! encounter a module that does not work with 1.1, please <a
! href="../../bug_report.html">let us know</a>.
!
!
! <h2>New Features with Apache 1.1</h2>
! <p>New features with this release, as extensions of the Apache
! functionality (see also more detailed <code>CHANGES</code> file in
! the source directory.) Because the core code has changed so
! significantly, there are certain liberties that earlier versions of
! Apache (and the NCSA daemon) took that recent Apache versions are
! pickier about - please check the <a
! href="../compat_notes.html">compatibility notes</a> if you have any
! problems.</p>
! <hr>
!
! <p>In addition to a number of bug fixes and internal performance
! enhancements, <a href="../../dist/">Apache
! 1.1</a> has the following specific new user features:</p>
<ul>
!
! <li><b><a href="keepalive.html">Support for Keep-Alive Persistent
! Connections</a></b><br> Apache now has (optional) support for persistent
! connections, as defined by the HTTP/1.1 draft. This protocol,
! supported by a number of current HTTP servers and browsers (including
! Netscape Navigator 2.0) has been shown to increase speed of document
! transfer by up to 50% in certain cases.
!
! <li><b><a href="host.html">New non-IP Intensive VirtualHost
! Support</a></b><br>
! Apache's support for virtual hosts has been enhanced to be able to
! use information sent by some new Web browsers to determine the server
! being accessed, without requiring an additional IP address for each
! host.
!
! <li><b><a href="bind.html">Listen to Multiple Addresses and
! Ports</a></b><br>
! Using the new <code>Listen</code> directive, Apache can listen to more
! than one port and IP address, using the same configuration set.
!
! <li><b><a href="mod_status.html">Status
! Module</a></b><br>
! Apache now contains a module that gives the webmaster accurate,
! up-to-date information about the server's status and its resource
! consumption. It also gives the current state of each server process
! including the current URL being processed. For an example, check out
! <A HREF="http://www.apache.org/status";>the status of the
! www.apache.org server</A>.
!
! <li><b><a href="mod_info.html">Server Information Module</a></b></br>
! This module gives a plethora of information about the other modules
! installed, their directives, and their configurations. It is
! extremely helpful in debugging configuration problems. For an
! example, check out <A
! HREF="http://www.apache.org/serv-info";>information about the
! www.apache.org server</A>.
!
! <li><b><a href="mod_proxy.html">Experimental Caching Proxy
Server</a></b><br>
! Apache can now act as
! an HTTP proxy server, allowing clients behind firewalls to use the
! server to access the outside world. In addition, it can cache
! documents it proxies, speeding up access to frequently requested
! documents.
!
! <li><b><a href="location.html">URL-based Access Protection</a></b><br>
! In addition to access checking and authorization by filename (with
! <code><a href="../core.html#directory"><Directory></a></code>),
! the new <code><Location></code> directive allows protection by
! URL.
!
! <li><b><a href="mod_actions.html">Filetype-based Script
"Actions"</a></b><br>
! You can now run CGI scripts whenever a file of a certain type is
! requested. This makes it much easier to execute scripts that process
! files. In addition, you can use the new <a
! href="mod_actions.html#script">Script</a> directive to enable scripts
! for files called with HTTP methods Apache does not natively support.
!
! <li><b><a href="handler.html">New "Handler" Directives</a></b><br>
! The new <code>AddHandler</code> and <code>SetHandler</code> directive
! allows "handlers" to be defined for filename extensions or
! directories. These handlers, which can either be built into Apache or
! added with the <a href="mod_actions.html">Action</a> directive, extend
! Apache's range of usability, and almost entirely remove the "magic"
! media types.
!
! <li><b><a href="mod_env.html">Customizable CGI Environment
! Variables</a></b><br>
! New <code>PassEnv</code> and <code>SetEnv</code> directives allow you to
! modify the environment variables passed to CGI scripts.
!
! <li><b><a href="mod_cern_meta.html">CERN Metafile Support</a></b><br>
! Now emulates the CERN httpd's support for metafiles containing additional
! HTTP headers to be supplied with a document.
!
! <li><b><a href="mod_imap.html">Improved Imagemap Support</a></b><br>
! The internal imagemap handling code has been rewritten and
! reorganized, adding new handling of default, base and relative URLs,
! and support for creating non-graphical menus for use with clients that
! do not support imagemaps.
!
! <li><b><a href="mod_userdir.html">Improved UserDir Directive</a></b><br>
! Now supports the ability to point user's files (as specificed by URLs
! beginning with the "<code>~</code>" character) at directories other
! than those specified by the Unix password file.
!
! <li><b>Minimal DNS Now Runtime Option</b><br>
! New <code>HostnameLookups</code>
! server configuration directive can be used to turn <code>On</code> or
! <code>Off</code> DNS lookups. This supercedes the -DMINIMAL_DNS
! compile-time configuration option. This option can be set per-directory.
!
! <li><b>IdentityCheck Now Per-Directory Option</b><br>
! The <code>IdentityCheck</code> directive, which controls the use of
! ident to check the remote user name, can now be set per directory. The
! ident support is also RFC 1413-compliant.
!
! <li><b>Redirect Now Usable in <code>.htaccess</code> Files</b><br>
! The <a href="../mod_alias.html#redirect"><code>Redirect</code></a>
! directive can now be used in <code>.htaccess</code> files when the
! <code>FileInfo</code> directive has been set on. This allows users to
! redirect parts of their directories without requiring CGI scripts
!
! <li><b>ErrorDocument Now Usable in <code>.htaccess</code> Files</b><br>
! The <a href="../custom-error.html"><code>ErrorDocument</code></a>
! directive can now be used in <code>.htaccess</code> files when the
! <code>FileInfo</code> directive has been set on. This allows users to
! have different error messages for different sections of a site.
!
! <li><b><code>ForceType</code> Directive</b><br>
! This new directive, in <code><Directory></code> sections or
! .htaccess files, allows you to override the filename extensions and
! force a single content type. (e.g. <code>ForceType
! application/octet-stream</code>)
!
! <li><b>File Owner Available to Included CGI Scripts</b><br>
! Server-side includes that call CGI scripts will now set a
! <code>USER_NAME</code> environment variable that contains the owner of
! the file which included it.
!
! <li><b>Improved Icons</b><br>
! Thanks to <a href="mailto:[EMAIL PROTECTED]">Kevin
! Hughes</a>, Apache's nifty color GIF icons for directory listings have
! been updated. In addition, the <a
! href="../../images/apache_pb.gif">Powered by Apache</a>
! (<code>apache_pb.gif</code>) logo has been included.
!
</ul>
+
<hr>
! <h3>New Authentication Modules</h3>
!
! <p><strong>Note:</strong> These modules are not
! compiled into the server by default, as they require special support
! on the host system. They must be enabled specifically in the
! <code>Configuration</code> file.</p>
!
<ul>
!
! <li><b><a href="mod_auth_anon.html">Anonymous HTTP Logins</a></b><br>
! New options allow you to allow, using Basic HTTP Authentication,
! anonymous logins, like those of FTP. This allows you to collect email
! addresses of people accessing your site.
!
! <li><b><a href="mod_digest.html">Support for Digest
! Authentication</a></b> [Documentation to be written]<br>
! Apache now supports digest authentication using RSA MD5
! encryption. When used with a supporting web browser, this provides a
! more secure alternative to Basic authentication.
!
! <li><strong><a href="mod_auth_db.html">Support for Unix DB
! Authentication</a></strong> - <code>mod_auth_db.c</code><br> In
! addition to <a href="../mod_auth_dbm.html">DBM</a> support, Apache now
! contains optional support for Berkeley DB databases.
!
! <li><strong><a href="mod_auth_msql.html">mSQL Database
! Authentication</a></strong> - <code>mod_auth_msql.html</code> <BR>
! Support for the use of mSQL databases for user authentication via HTTP
! is now supported.
!
</ul>
! <hr>
!
! <h3>OS/2 Support</h3>
!
! <p>Apache now includes support for OS/2, thanks to <a
href="http://www.slink.com/ApacheOS2/";>Softlink Services.</a></p>
!
! <hr>
!
! <A HREF="../../"><img src="../../images/apache_home.gif" ALT="Home"></A>
! <A HREF="../"><IMG SRC="../../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
1.2 +231 -29 apache/docs/mod_imap.html
Index: mod_imap.html
===================================================================
RCS file: /export/home/cvs/apache/docs/mod_imap.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** mod_imap.html 1996/11/17 20:22:52 1.1
--- mod_imap.html 1996/11/17 20:27:06 1.2
***************
*** 13,28 ****
This module is contained in the <code>mod_imap.c</code> file, and
is compiled in by default. It provides for <code>.map</code> files,
replacing the functionality of the <code>imagemap</code> CGI program. Any
! document with mime type <code>application/x-httpd-imap</code> will be
processed by this module.
- <!--%plaintext <?INDEX {\tt application/x-httpd-imap} mime type> -->
<h2>Summary</h2>
! In order to use server-parsed imagemap files, you must first
! compile the module into your server, and add the following line
! to the server configuration file. This entry indicates that imagemap
! files will be named with a <code>.map</code> extension.
! <blockquote><code>AddType application/x-httpd-imap map</code></blockquote>
<H2>New Features</H2>
The imagemap module adds some new features that were not
--- 13,40 ----
This module is contained in the <code>mod_imap.c</code> file, and
is compiled in by default. It provides for <code>.map</code> files,
replacing the functionality of the <code>imagemap</code> CGI program. Any
! directory or document type configured to use the handler
<code>imap-file</code>
! (using either <code><A
! HREF="http://www.apache.org/docs/mod_mime.html#addhandler";>AddHandler</A>
! </code> or <code><A
!
HREF="http://www.apache.org/docs/mod_mime.html#sethandler";>SetHandler</A></code>)
!
! will be
processed by this module.
<h2>Summary</h2>
!
! This module is in the default Apache distribution. The following directive
will
! activate files ending with <code>.map</code> as imagemap files:
!
! <blockquote><code>AddHandler imap-file map</code></blockquote>
!
! Note that the following is still supported:
!
! <blockquote><code>AddType application/x-httpd-imap map</code></blockquote>
!
! However, we are trying to phase out "magic MIME types" so we are deprecating
! this method.
<H2>New Features</H2>
The imagemap module adds some new features that were not
***************
*** 30,70 ****
<ul>
<LI>URL references relative to the Referer: information.
! <LI>Default <BASE> assignment through a new map field
! <code>base_uri</code>.
<LI>No need for <code>imagemap.conf</code> file.
<LI>Point references.
</ul>
<P>
! <code>base_uri</code> options:<P>
<dl>
! <dt><code>map</code>
! <dd>Provides the default and old behaviour of <I>map relative</I>
! reference.<P>
! <dt><code>referer</code>
! <dd>Uses the Referer: header information to reference a URL relative to
! the current document.<P>
! <dt><code>http://whateverurl</code>
! <dd>Has the effect of setting <BASE> to that URL making all references
! relative to that <BASE>.<P>
</dl>
! <h3>Mapfile Example</h3>
<blockquote><code>
! default http:/lincoln/ <br>
! base_uri referer <br>
! rect .. 0,0 77,27 <br>
! poly http://www.inetnebr.com/ 78,0 194,27 <br>
circle http://www.inetnebr.com/lincoln/feedback/ 195,0 305,27 <br>
! rect search_index 306,0 419,27 <br>
! point http://www.zyzzyva.com/ 420,0 549,27
</code></blockquote>
<P>
! <h3>Referencing your mapfile</h3>
<blockquote><code>
! <A HREF="http:/maps/imagmap1.map"> <br>
! <IMG ISMAP SRC="http:/images/imagemap1.gif"> <br>
</A>
</code></blockquote><p>
<!--%hypertext -->
--- 42,271 ----
<ul>
<LI>URL references relative to the Referer: information.
! <LI>Default <BASE> assignment through a new map directive
! <code>base</code>.
<LI>No need for <code>imagemap.conf</code> file.
<LI>Point references.
+ <LI>Configurable generation of imagemap menus.
</ul>
<P>
!
! <h2>Configuration Directives</h2>
! <ul>
! <li><A HREF="#imapmenu">ImapMenu</A>
! <li><A HREF="#imapdefault">ImapDefault</A>
! <li><A HREF="#imapbase">ImapBase</A>
! </ul>
!
!
! <p>
!
! <A name="imapmenu"><h3>ImapMenu</h3></A>
! <strong>Syntax:</strong> ImapMenu <code>{none, formatted, semiformatted,
!
unformatted}</code><br>
! <Strong>Context:</strong> server config, virtual host, directory,
.htaccess<br>
! <Strong>Override:</strong> Indexes<br>
! <strong>Module:</strong> mod_imap.c<p>
!
! The ImapMenu directive determines the action taken if an imagemap file
! is called without valid coordinates.
<dl>
! <dt><code>none</code>
! <dd>If ImapMenu is
! <code>none</code>, no menu is generated, and the <code>default</code>
! action is performed.
! <dt><code>formatted</code>
! <dd>A <code>formatted</code> menu is the simplest menu. Comments
! in the imagemap file are ignored. A level one header is
! printed, then an hrule, then the links each on a separate line.
! The menu has a consistent, plain look close to that of
! a directory listing.
! <dt><code>semiformatted</code>
! <dd>In the <code>semiformatted</code> menu, comments are printed
! where they occur in the imagemap file. Blank lines are turned
! into HTML breaks. No header or hrule is printed, but otherwise
! the menu is the same as a <code>formatted</code> menu.
! <dt><code>unformatted</code>
! <dd>Comments are printed, blank lines are ignored. Nothing is
! printed that does not appear in the imagemap file. All breaks
! and headers must be included as comments in the imagemap file.
! This gives you the most flexibility over the appearance of your
! menus, but requires you to treat your map files as HTML instead
! of plaintext.
</dl>
! <p>
!
! <A name="imapdefault"><h3>ImapDefault</h3></A>
! <strong>Syntax:</strong> ImapDefault <code>{error, nocontent,
! map, referer,
URL}</code><br>
! <Strong>Context:</strong> server config, virtual host, directory,
.htaccess<br>
! <Strong>Override:</strong> Indexes<br>
! <strong>Module:</strong> mod_imap.c<p>
!
!
! The ImapDefault directive sets the default <code>default</code> used in
! the imagemap files. It's value is overridden by a <code>default</code>
! directive within the imagemap file. If not present, the
! <code>default</code> action is <code>nocontent</code>, which means
! that a <code>204 No Content</code> is sent to the client. In this
! case, the client should continue to display the original page.
!
! <p>
!
! <A name="imapbase"><h3>ImapBase</h3></A>
! <strong>Syntax:</strong> ImapBase <code>{map, referer, URL}</code><br>
! <Strong>Context:</strong> server config, virtual host, directory,
.htaccess<br>
! <Strong>Override:</strong> Indexes<br>
! <strong>Module:</strong> mod_imap.c<p>
!
! The ImapBase directive sets the default <code>base</code> used in
! the imagemap files. It's value is overridden by a <code>base</code>
! directive within the imagemap file. If not present, the
! <code>base</code> defaults to <code>http://servername/</code>.
!
! <hr>
! <p>
!
! <h2>Imagemap File</h2>
! The lines in the imagemap files can have one of several formats:
! <blockquote>
! <code>directive value [x,y ...]</code><br>
! <code>directive value "Menu text" [x,y ...]</code><br>
! <code>directive value x,y ... "Menu text"</code><br>
! </blockquote>
! The directive is one of <code>base</code>, <code>default</code>,
! <code>poly</code>, <code>circle</code>, <code>rect</code>, or
! <code>point</code>. The value is an absolute or relative URL, or one
! of the special values listed below. The coordinates are
! <code>x,y</code> pairs seperated by whitespace. The quoted text is
! used as the text of the link if a imagemap menu is generated. Lines
! beginning with '#' are comments.
!
! <h3>Imagemap File Directives</h3>
! There are six directives allowed in the imagemap file. The directives
! can come in any order, but are processed in the order they are found
! in the imagemap file.
! <dl>
! <dt><code>base</code> Directive
! <dd>Has the effect of <code><BASE href="value"></code>. The
! non-absolute URLs of the mapfile are taken relative to this value.
! The <code>base</code> directive overrides ImapBase as set in a
! .htaccess file or in the server configuration files. In the absence
! of an ImapBase configuration directive, <code>base</code> defaults to
! <code>http://server_name/</code>. <br>
! <code>base_uri</code> is synonymous with <code>base</code>. Note that
! a trailing slash on the URL is significant.
! <p>
! <dt><code>default</code> Directive
! <dd>The action taken if the coordinates given do not fit any of the
! <code>poly</code>, <code>circle</code> or <code>rect</code>
! directives, and there are no <code>point</code> directives. Defaults
! to <code>nocontent</code> in the absence of an ImapDefault
! configuration setting, causing a status code of <code>204 No
! Content</code> to be returned. The client should keep the same
! page displayed.
! <p>
! <dt><code>poly</code> Directive
! <dd>Takes three to one-hundred points, and is obeyed if the user selected
! coordinates fall within the polygon defined by these points.
! <p>
! <dt><code>circle</code>
! <dd>Takes the center coordinates of a circle and a point on the circle. Is
! obeyed if the user selected point is with the circle.
! <p>
! <dt><code>rect</code> Directive
! <dd>Takes the coordinates of two opposing corners of a rectangle. Obeyed
! if the point selected is within this rectangle.
! <p>
! <dt><code>point</code> Directive
! <dd>Takes a single point. The point directive closest to the user
! selected point is obeyed if no other directives are satisfied.
! Note that <code>default</code> will not be followed if a
! <code>point</code> directive is present and valid coordinates are
! given.
! </dl>
!
!
!
! <h3>Values</h3>
! The values for each of the directives can any of the following:
! <dl>
! <dt>a URL
! <dd>The URL can be relative or absolute URL. Relative URLs can
! contain '..' syntax and will be resolved relative to the
! <code>base</code> value. <br>
! <code>base</code> itself will not resolved according to the current
! value. A statement <code>base mailto:</code> will work properly,
though.
! <p>
! <dt><code>map</code>
! <dd>Equivalent to the URL of the imagemap file itself. No
! coordinates are sent with this, so a menu will be generated
! unless ImapMenu is set to 'none'.
! <p>
! <dt><code>menu</code>
! <dd>Synonymous with <code>map</code>.
! <p>
! <dt><code>referer</code>
! <dd>Equivalent to the URL of the refering document.
! Defaults to <code>http://servername/</code> if no Referer:
! header was present.
! <p>
! <dt><code>nocontent</code>
! <dd>Sends a status code of <code>204 No Content</code>,
! telling the client to keep the same page displayed. Valid for
! all but <code>base</code>.
! <p>
! <dt><code>error</code>
! <dd>Fails with a <code>500 Server Error</code>. Valid for all but
! <code>base</code>, but sort of silly for anything but
! <code>default</code>.
! </dl>
!
! <h3>Coordinates</h3>
! <dl>
! <dt><code>0,0 200,200</code>
! <dd>A coordinate consists of an <tt>x</tt> and a <tt>y</tt> value
! separated by a comma. The coordinates are separated from each other
! by whitespace. To accomodate the way Lynx handles imagemaps, should
a
! user select the coordinate <code>0,0</code>, it is as if
! no coordinate had been selected.
! </dl>
!
! <h3>Quoted Text</h3>
! <dl>
! <dt><code>"Menu Text"</code>
! <dd>After the value or after the coordinates, the line optionally may
! contain text within double quotes. This string is used as the
! text for the link if a menu is generated:<br>
! <code><a href="http://foo.com/">Menu text</a></code><br>
! If no quoted text is present, the name of the link will be used
! as the text:<br>
! <code><a
href="http://foo.com/">http://foo.com</a></code><br>
! It is impossible to escape double quotes within this text.
! </dl>
!
! <hr>
!
! <h2>Example Mapfile</h2>
<blockquote><code>
! #Comments are printed in a 'formatted' or 'semiformatted' menu. <br>
! #And can contain html tags. <hr> <br>
! base referer <br>
! poly map "Could I have a menu, please?" 0,0 0,10 10,10 10,0 <br>
! rect .. 0,0 77,27 "the directory of the referer"<br>
circle http://www.inetnebr.com/lincoln/feedback/ 195,0 305,27 <br>
! rect another_file "in same directory as referer" 306,0 419,27 <br>
! point http://www.zyzzyva.com/ 100,100 <br>
! point http://www.tripod.com/ 200,200 <br>
! rect mailto:[EMAIL PROTECTED] 100,150 200,0 "Bugs?" <br>
</code></blockquote>
<P>
! <h2>Referencing your mapfile</h2>
<blockquote><code>
! <A HREF="/maps/imagmap1.map"> <br>
! <IMG ISMAP SRC="/images/imagemap1.gif"> <br>
</A>
</code></blockquote><p>
<!--%hypertext -->
***************
*** 74,76 ****
--- 275,278 ----
</BODY>
</HTML>
<!--/%hypertext -->
+
1.2 +17 -14 apache/docs/mod_userdir.html
Index: mod_userdir.html
===================================================================
RCS file: /export/home/cvs/apache/docs/mod_userdir.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** mod_userdir.html 1996/11/17 20:22:56 1.1
--- mod_userdir.html 1996/11/17 20:27:08 1.2
***************
*** 6,12 ****
</HEAD>
<BODY>
! <IMG SRC="../images/apache_sub.gif" ALT="">
<!--/%hypertext -->
<H1>Module mod_userdir</h1>
--- 6,12 ----
</HEAD>
<BODY>
! <IMG SRC="../../images/apache_sub.gif" ALT="">
<!--/%hypertext -->
<H1>Module mod_userdir</h1>
***************
*** 22,28 ****
<A name="userdir"><h2>UserDir</h2></A>
<!--%plaintext <?INDEX {\tt UserDir} directive> -->
! <strong>Syntax:</strong> UserDir <em>directory</em><br>
<strong>Default:</strong> <code>UserDir public_html</code><br>
<Strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> Base<br>
--- 22,28 ----
<A name="userdir"><h2>UserDir</h2></A>
<!--%plaintext <?INDEX {\tt UserDir} directive> -->
! <strong>Syntax:</strong> UserDir <em>directory/filename</em><br>
<strong>Default:</strong> <code>UserDir public_html</code><br>
<Strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> Base<br>
***************
*** 31,50 ****
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.
<em>Directory</em> is either <code>disabled</code>, to disable this feature,
! or the name of a directory. If not disabled, then a request for a URL
! beginning with <code>http://myserver/~</code><em>unix-username</em> will
! be translated to a filename beginning with <em>home-dir/directory</em>,
! where <em>home-dir</em> is the home directory for user
<em>unix-username</em>.
! Example:
! <blockquote><code>UserDir public_html</code></blockquote>
! Then a request for <code>http://myserver/~foo56/adir/file.html</code>
! will return the file
! <code>http://myserver/home/foo56/public_html/adir/file.html</code>.<p>
!
<!--%hypertext -->
<hr>
! <A HREF="../"><IMG SRC="../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
--- 31,53 ----
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.
<em>Directory</em> is either <code>disabled</code>, to disable this feature,
! or the name of a directory, following one of the following
! patterns. If not disabled, then a request for
! <code>http://www.foo.com/~bar/one/two.html</code> will be translated to:
! <pre>
! UserDir public_html -> ~bar/public_html/one/two.html
! UserDir /usr/web -> /usr/web/bar/one/two.html
! UserDir /home/*/www -> /home/bar/www/one/two.html
! </pre>
! The following directives will send redirects to the client:
! <pre>
! UserDir http://www.x.com/users -> http//www.x.com/users/bar/one/two.html
! UserDir http://www.x.com/*/y -> http://www.x.com/y/one/two.html
! </pre>
<!--%hypertext -->
<hr>
! <A HREF="../../"><IMG SRC="../../images/apache_home.gif" ALT="Home"></A>
! <A HREF="./"><IMG SRC="../../images/apache_index.gif" ALT="Index"></A>
</BODY>
</HTML>
