diff options
| -rw-r--r-- | usr.sbin/httpd/htdocs/manual/howto/htaccess.html | 422 | ||||
| -rw-r--r-- | usr.sbin/httpd/htdocs/manual/mod/mod_alias.html.en | 395 | ||||
| -rw-r--r-- | usr.sbin/httpd/htdocs/manual/mod/mod_alias.html.ja.jis | 397 | ||||
| -rw-r--r-- | usr.sbin/httpd/htdocs/manual/mod/mod_auth.html.en | 322 | ||||
| -rw-r--r-- | usr.sbin/httpd/htdocs/manual/mod/mod_auth.html.ja.jis | 335 | ||||
| -rw-r--r-- | usr.sbin/httpd/src/os/tpf/samples/linkhttp.dlm | 66 |
6 files changed, 1937 insertions, 0 deletions
diff --git a/usr.sbin/httpd/htdocs/manual/howto/htaccess.html b/usr.sbin/httpd/htdocs/manual/howto/htaccess.html new file mode 100644 index 00000000000..2233d0b09c7 --- /dev/null +++ b/usr.sbin/httpd/htdocs/manual/howto/htaccess.html @@ -0,0 +1,422 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta name="generator" content="HTML Tidy, see www.w3.org" /> + + <title>Apache Tutorial: .htaccess files</title> + </head> + + <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#000080" + alink="#FF0000"> + <div align="CENTER"> + <img src="../images/sub.gif" alt="[APACHE DOCUMENTATION]" /> + + <h3>Apache HTTP Server Version 1.3</h3> + </div> + + + + <h1 align="CENTER"><code>.htaccess</code> files</h1> + <!-- INDEX BEGIN --> + + <ul> + <li><a href="#what">What they are/How to use them</a></li> + + <li><a href="#when">When (not) to use <code + class="file">.htaccess</code></a> files</li> + + <li><a href="#how">How directives are applied</a></li> + + <li><a href="#auth">Authentication example</a></li> + + <li><a href="#ssi">Server side includes example</a></li> + + <li><a href="#cgi">CGI example</a></li> + + <li><a href="#troubleshoot">Troubleshooting</a></li> + </ul> + <!-- Index End --> + + <table border="1"> + <tr> + <td valign="top"><strong>Related Modules</strong><br /> + <br /> + <code><a href="../mod/core.html">core</a></code><br /> + <code><a href="../mod/mod_auth.html">mod_auth</a></code><br /> + <code><a href="../mod/mod_cgi.html">mod_cgi</a></code><br /> + <code><a href="../mod/mod_includes.html">mod_includes</a><br /> + </code> <a href="../mod/mod_mime.html">mod_mine</a><br /> + </td> + + <td valign="top"><strong>Related Directives</strong><br /> + <br /> + <code><a + href="../mod/core.html#accessfilename">AccessFileName</a></code><br /> + <code><a + href="../mod/core.html#allowoverride">AllowOverride</a></code><br /> + <code><a href="../mod/core.html#options">Options</a></code><br /> + <code><a + href="../mod/mod_mime.html#addhandler">AddHandler</a></code><br /> + <code><a + href="../mod/core.html#sethandler">SetHandler</a></code><br /> + <code><a + href="../mod/core.html#authtype">AuthType</a></code><br /> + <code><a + href="../mod/core.html#authname">AuthName</a></code><br /> + <code><a + href="../mod/mod_auth.html#authuserfile">AuthUserFile</a></code><br /> + <code><a + href="../mod/mod_auth.html#authuserfile">AuthGroupFile</a></code><br /> + <code><a href="../mod/core.html#require">Require</a></code><br /> + </td> + </tr> + </table> + <hr /> + + <h2><a id="what" name="what">What they are/How to use them</a></h2> + + <p><code>.htaccess</code> files (or "distributed configuration files") + provide a way to make configuration changes on a per-directory basis. A + file, containing one or more configuration directives, is placed in a + particular document directory, and the directives apply to that + directory, and all subdirectories thereof.</p> + + <p>Note: If you want to call your <code>.htaccess</code> file something + else, you can change the name of the file using the <code><a + href="../mod/core.html#accessfilename">AccessFileName</a></code> + directive. For example, if you would rather call the file + <code>.config</code> then you can put the following in your server + configuration file:</p> + + <blockquote> + <table cellpadding="10"> + <tr> + <td bgcolor="#eeeeee"><code>AccessFileName .config</code> </td> + </tr> + </table> + </blockquote> + + <p>What you can put in these files is determined by the <code><a + href="../mod/core.html#allowoverride">AllowOverride</a></code> + directive. This directive specifies, in categories, what directives + will be honored if they are found in a <code>.htaccess</code> file. If + a directive is permitted in a <code>.htaccess</code> file, the + documentation for that directive will contain an Override section, + specifying what value must be in <code>AllowOverride</code> in order + for that directive to be permitted.</p> + + <p>For example, if you look at the documentation for the <a + href="../mod/core.html#adddefaultcharset">AddDefaultCharset</a> + directive, you will find that it is permitted in <code>.htaccess</code> + files. (See the Context line in the directive summary.) The <a + href="../mod/directive-dict.html#Context">Override</a> line reads + "<code>FileInfo</code>". Thus, you must have at least + "<code>AllowOverride FileInfo</code>" in order for this directive to be + honored in <code>.htaccess</code> files.</p> + + <p>Example:</p> + + <blockquote> + <table> + <tr> + <td><a + href="../mod/directive-dict.html#Context">Context:</a></td> + + <td>server config, virtual host, directory, .htaccess</td> + </tr> + + <tr> + <td><a + href="../mod/directive-dict.html#Override">Override:</a></td> + + <td>FileInfo</td> + </tr> + </table> + </blockquote> + + <p>If you are unsure whether a particular directive is permitted in a + <code>.htaccess</code> file, look at the documentation for that + directive, and check the Context line for ".htaccess."</p> + + <h2><a id="when" name="when">When (not) to use .htaccess files</a></h2> + + <p>In general, you should never use <code>.htaccess</code> files unless + you don't have access to the main server configuration file. There is, + for example, a prevailing misconception that user authentication should + always be done in <code>.htaccess</code> files. This is simply not the + case. You can put user authentication configurations in the main server + configuration, and this is, in fact, the preferred way to do + things.</p> + + <p><code>.htaccess</code> files should be used in a case where the + content providers need to make configuration changes to the server on a + per-directory basis, but do not have root access on the server system. + In the event that the server administrator is not willing to make + frequent configuration changes, it might be desirable to permit + individual users to make these changes in <code>.htaccess</code> files + for themselves. This is particularly true, for example, in cases where + ISPs are hosting multiple user sites on a single machine, and want + their users to be able to alter their configuration.</p> + + <p>However, in general, use of <code>.htaccess</code> files should be + avoided when possible. Any configuration that you would consider + putting in a <code>.htaccess</code> file, can just as effectively be + made in a <a href="../mod/core.html#Directory"><Directory></a> + section in your main server configuration file.</p> + + <p>There are two main reasons to avoid the use of + <code>.htaccess</code> files.</p> + + <p>The first of these is performance. When <code>AllowOverride</code> + is set to allow the use of <code>.htaccess</code> files, Apache will + look in every directory for <code>.htaccess</code> files. Thus, + permitting <code>.htaccess</code> files causes a performance hit, + whether or not you actually even use them! Also, the + <code>.htaccess</code> file is loaded every time a document is + requested.</p> + + <p>Further note that Apache must look for <code>.htaccess</code> files + in all higher-level directories, in order to have a full complement of + directives that it must apply. (See section on <a href="#how">how + directives are applied</a>.) Thus, if a file is requested out of a + directory <code>/www/htdocs/example</code>, Apache must look for the + following files:</p> + + <blockquote> + <table cellpadding="10"> + <tr> + <td bgcolor="#eeeeee"><code>/.htaccess<br /> + /www/.htaccess<br /> + /www/htdocs/.htaccess<br /> + /www/htdocs/example/.htaccess</code> </td> + </tr> + </table> + </blockquote> + + <p>And so, for each file access out of that directory, there are 4 + additional file-system accesses, even if none of those files are + present. (Note that this would only be the case if .htaccess files were + enabled for /, which is not usually the case.)</p> + + <p>The second consideration is one of security. You are permitting + users to modify server configuration, which may result in changes over + which you have no control. Carefully consider whether you want to give + your users this privilege.</p> + + <p>Note that it is completely equivalent to put a .htaccess file in a + directory <code>/www/htdocs/example</code> containing a directive, and + to put that same directive in a Directory section <code><Directory + /www/htdocs/example></code> in your main server configuration:</p> + + <p><code>.htaccess</code> file in <code>/www/htdocs/example</code>:</p> + + <blockquote> + <table cellpadding="10"> + <tr> + <td bgcolor="#eeeeee"><code>AddType text/example .exm</code> + </td> + </tr> + </table> + </blockquote> + + <p><code>httpd.conf</code></p> + + <blockquote> + <table cellpadding="10"> + <tr> + <td bgcolor="#eeeeee"><code><Directory + /www/htdocs/example><br /> + AddType text/example .exm<br /> + </Directory></code> </td> + </tr> + </table> + </blockquote> + + <p>However, putting this configuration in your server configuration + file will result in less of a performance hit, as the configuration is + loaded once when Apache starts, rather than every time a file is + requested.</p> + + <p>The use of <code>.htaccess</code> files can be disabled completely + by setting the <code>AllowOverride</code> directive to "none"</p> + + <blockquote> + <table cellpadding="10"> + <tr> + <td bgcolor="#eeeeee"><code>AllowOverride None</code> </td> + </tr> + </table> + </blockquote> + + <h2><a id="how" name="how">How directives are applied</a></h2> + + <p>The configuration directives found in a <code>.htaccess</code> file + are applied to the directory in which the <code>.htaccess</code> file + is found, and to all subdirectories thereof. However, it is important + to also remember that there may have been <code>.htaccess</code> files + in directories higher up. Directives are applied in the order that they + are found. Therefore, a <code>.htaccess</code> file in a particular + directory may override directives found in <code>.htaccess</code> files + found higher up in the directory tree. And those, in turn, may have + overridden directives found yet higher up, or in the main server + configuration file itself.</p> + + <p>Example:</p> + + <p>In the directory <code>/www/htdocs/example1</code> we have a + <code>.htaccess</code> file containing the following:</p> + + <blockquote> + <table cellpadding="10"> + <tr> + <td bgcolor="#eeeeee"><code>Options +ExecCGI</code> </td> + </tr> + </table> + </blockquote> + + <p>(Note: you must have "<code>AllowOverride Options</code>" in effect + to permit the use of the "<code><a + href="../mod/core.html#options">Options</a></code>" directive in + <code>.htaccess</code> files.)</p> + + <p>In the directory <code>/www/htdocs/example1/example2</code> we have + a <code>.htaccess</code> file containing:</p> + + <blockquote> + <table cellpadding="10"> + <tr> + <td bgcolor="#eeeeee"><code>Options Includes</code> </td> + </tr> + </table> + </blockquote> + + <p>Because of this second <code>.htaccess</code> file, in the directory + <code>/www/htdocs/example1/example2</code>, CGI execution is not + permitted, as only <code>Options Includes</code> is in effect, which + completely overrides any earlier setting that may have been in + place.</p> + + <h2><a id="auth" name="auth">Authentication example</a></h2> + + <p>If you jumped directly to this part of the document to find out how + to do authentication, it is important to note one thing. There is a + common misconception that you are required to use + <code>.htaccess</code> files in order to implement password + authentication. This is not the case. Putting authentication directives + in a <code><Directory></code> section, in your main server + configuration file, is the preferred way to implement this, and + <code>.htaccess</code> files should be used only if you don't have + access to the main server configuration file. See above for a + discussion of when you should and should not use <code>.htaccess</code> + files.</p> + + <p>Having said that, if you still think you need to use a + <code>.htaccess</code> file, you may find that a configuration such as + what follows may work for you.</p> + + <p>You must have "<code>AllowOverride AuthConfig</code>" in effect for + these directives to be honored.</p> + + <p><code>.htaccess</code> file contents:</p> + + <blockquote> + <table cellpadding="10"> + <tr> + <td bgcolor="#eeeeee"><code>AuthType Basic<br /> + AuthName "Password Required"<br /> + AuthUserFile /www/passwords/password.file<br /> + AuthGroupFile /www/passwords/group.file<br /> + Require Group admins</code> </td> + </tr> + </table> + </blockquote> + + <p>Note that <code>AllowOverride AuthConfig</code> must be in effect + for these directives to have any effect.</p> + + <p>Please see the <a href="auth.html">authentication tutorial</a> for a + more complete discussion of authentication and authorization.</p> + + <h2><a id="ssi" name="ssi">Server side includes example</a></h2> + + <p>Another common use of <code>.htaccess</code> files is to enable + Server Side Includes for a particular directory. This may be done with + the following configuration directives, placed in a + <code>.htaccess</code> file in the desired directory:</p> + + <blockquote> + <table cellpadding="10"> + <tr> + <td bgcolor="#eeeeee"><code>Options +Includes<br /> + AddType text/html shtml<br /> + AddHandler server-parsed shtml</code> </td> + </tr> + </table> + </blockquote> + + <p>Note that <code>AllowOverride Options</code> and <code>AllowOverride + FileInfo</code> must both be in effect for these directives to have any + effect.</p> + + <p>Please see the <a href="ssi.html">SSI tutorial</a> for a more + complete discussion of server-side includes.</p> + + <h2><a id="cgi" name="cgi">CGI example</a></h2> + + <p>Finally, you may wish to use a <code>.htaccess</code> file to permit + the execution of CGI programs in a particular directory. This may be + implemented with the following configuration:</p> + + <blockquote> + <table cellpadding="10"> + <tr> + <td bgcolor="#eeeeee"><code>Options +ExecCGI<br /> + AddHandler cgi-script cgi pl</code> </td> + </tr> + </table> + </blockquote> + + <p>Alternately, if you wish to have all files in the given directory be + considered to be CGI programs, this may be done with the following + configuration:</p> + + <blockquote> + <table cellpadding="10"> + <tr> + <td bgcolor="#eeeeee"><code>Options +ExecCGI<br /> + SetHandler cgi-script</code> </td> + </tr> + </table> + </blockquote> + + <p>Note that <code>AllowOverride Options</code> must be in effect for + these directives to have any effect.</p> + + <p>Please see the <a href="cgi.html">CGI tutorial</a> for a more + complete discussion of CGI programming and configuration.</p> + + <h2><a id="troubleshoot" name="troubleshoot">Troubleshooting</a></h2> + + <p>When you put configuration directives in a <code>.htaccess</code> + file, and you don't get the desired effect, there are a number of + things that may be going wrong.</p> + + <p>Most commonly, the problem is that <code><a + href="../mod/core.html#allowoverride">AllowOverride</a></code> is not + set such that your configuration directives are being honored. Make + sure that you don't have a <code>AllowOverride None</code> in effect + for the file scope in question. A good test for this is to put garbage + in your <code>.htaccess</code> file and reload. If a server error is + not generated, then you almost certainly have <code>AllowOverride + None</code> in effect.</p> + + <p>If, on the other hand, you are getting server errors when trying to + access documents, check your Apache error log. It will likely tell you + that the directive used in your .htaccess file is not permitted. + Alternately, it may tell you that you had a syntax error, which you + will then need to fix.</p> + </body> +</html> + diff --git a/usr.sbin/httpd/htdocs/manual/mod/mod_alias.html.en b/usr.sbin/httpd/htdocs/manual/mod/mod_alias.html.en new file mode 100644 index 00000000000..3a39c6dc001 --- /dev/null +++ b/usr.sbin/httpd/htdocs/manual/mod/mod_alias.html.en @@ -0,0 +1,395 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta name="generator" content="HTML Tidy, see www.w3.org" /> + + <title>Apache module mod_alias</title> + </head> + <!-- Background white, links blue (unvisited), navy (visited), red (active) --> + + <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" + vlink="#000080" alink="#FF0000"> + <div align="CENTER"> + <img src="../images/sub.gif" alt="[APACHE DOCUMENTATION]" /> + + <h3>Apache HTTP Server Version 1.3</h3> + </div> + + + <h1 align="CENTER">Module mod_alias</h1> + + <p>This module provides for mapping different parts of the host + filesystem in the document tree, and for URL redirection.</p> + + <p><a href="module-dict.html#Status" + rel="Help"><strong>Status:</strong></a> Base<br /> + <a href="module-dict.html#SourceFile" + rel="Help"><strong>Source File:</strong></a> mod_alias.c<br /> + <a href="module-dict.html#ModuleIdentifier" + rel="Help"><strong>Module Identifier:</strong></a> + alias_module</p> + + <h2>Summary</h2> + + <p>The directives contained in this module allow for + manipulation and control of URLs as requests arrive at the + server. The <code>Alias</code> and <code>ScriptAlias</code> + directives are used to map between URLs and filesystem paths. + This allows for content which is not directly under the <a + href="core.html#documentroot"><code>DocumentRoot</code></a> to + be served as part of the web document tree. The + <code>ScriptAlias</code> directive has the additional effect of + marking the target directory as containing only CGI + scripts.</p> + + <p>The <code>Redirect</code> directives are used to instruct + clients to make a new request with a different URL. They are + often used when a resource has moved to a new location.</p> + + <p>A more powerful and flexible set of directives for + manipulating URLs is contained in the <a + href="mod_rewrite.html"><code>mod_rewrite</code></a> + module.</p> + + <h2>Directives</h2> + + <ul> + <li><a href="#alias">Alias</a></li> + + <li><a href="#aliasmatch">AliasMatch</a></li> + + <li><a href="#redirect">Redirect</a></li> + + <li><a href="#redirectmatch">RedirectMatch</a></li> + + <li><a href="#redirecttemp">RedirectTemp</a></li> + + <li><a href="#redirectperm">RedirectPermanent</a></li> + + <li><a href="#scriptalias">ScriptAlias</a></li> + + <li><a href="#scriptaliasmatch">ScriptAliasMatch</a></li> + </ul> + <hr /> + + <h2><a id="alias" name="alias">Alias directive</a></h2> + + <p> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>Syntax:</strong></a> Alias <em>URL-path + file-path</em>|<em>directory-path</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>Context:</strong></a> server config, virtual + host<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>Status:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>Module:</strong></a> mod_alias</p> + + <p>The Alias directive allows documents to be stored in the + local filesystem other than under the <a + href="core.html#documentroot">DocumentRoot</a>. URLs with a + (%-decoded) path beginning with <em>url-path</em> will be + mapped to local files beginning with + <em>directory-filename</em>.</p> + + <p>Example:</p> + + <blockquote> + <code>Alias /image /ftp/pub/image</code> + </blockquote> + + <p>A request for http://myserver/image/foo.gif would cause the + server to return the file /ftp/pub/image/foo.gif.</p> + + <p>Note that if you include a trailing / on the + <em>url-path</em> then the server will require a trailing / in + order to expand the alias. That is, if you use <code>Alias + /icons/ /usr/local/apache/icons/</code> then the url + <code>/icons</code> will not be aliased.</p> + + <p>Note that you may need to specify additional <a + href="core.html#directory"><code><Directory></code></a> + sections which cover the <em>destination</em> of aliases. + Aliasing occurs before <code><Directory></code> sections + are checked, so only the destination of aliases are affected. + (Note however <a + href="core.html#location"><code><Location></code></a> + sections are run through once before aliases are performed, so + they will apply.)</p> + + <p>See also <a href="#scriptalias">ScriptAlias</a>.</p> + <hr /> + + <h2><a id="aliasmatch" name="aliasmatch">AliasMatch</a></h2> + + <p><a href="directive-dict.html#Syntax" + rel="Help"><strong>Syntax:</strong></a> AliasMatch <em>regex + file-path</em>|<em>directory-path</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>Context:</strong></a> server config, virtual + host<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>Status:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>Module:</strong></a> mod_alias<br /> + <a href="directive-dict.html#Compatibility" + rel="Help"><strong>Compatibility:</strong></a> Available in + Apache 1.3 and later</p> + + <p>This directive is equivalent to <a href="#alias">Alias</a>, + but makes use of standard regular expressions, instead of + simple prefix matching. The supplied regular expression is + matched against the URL-path, and if it matches, the server + will substitute any parenthesized matches into the given string + and use it as a filename. For example, to activate the + <code>/icons</code> directory, one might use:</p> +<pre> + AliasMatch ^/icons(.*) /usr/local/apache/icons$1 +</pre> + <hr /> + + <h2><a id="redirect" name="redirect">Redirect + directive</a></h2> + + <p> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>Syntax:</strong></a> Redirect + [<em>status</em>] <em>URL-path URL</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>Context:</strong></a> server config, virtual + host, directory, .htaccess<br /> + <a href="directive-dict.html#Override" + rel="Help"><strong>Override:</strong></a> FileInfo<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>Status:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>Module:</strong></a> mod_alias<br /> + <a href="directive-dict.html#Compatibility" + rel="Help"><strong>Compatibility:</strong></a> The directory + and .htaccess context's are only available in versions 1.1 and + later. The <em>status</em> argument is only available in Apache + 1.2 or later.</p> + + <p>The Redirect directive maps an old URL into a new one. The + new URL is returned to the client which attempts to fetch it + again with the new address. <em>URL-path</em> a (%-decoded) + path; any requests for documents beginning with this path will + be returned a redirect error to a new (%-encoded) URL beginning + with <em>URL</em>.</p> + + <p>Example:</p> + + <blockquote> + <code>Redirect /service http://foo2.bar.com/service</code> + </blockquote> + + <p>If the client requests http://myserver/service/foo.txt, it + will be told to access http://foo2.bar.com/service/foo.txt + instead.</p> + + <p><strong>Note:</strong> Redirect directives take precedence + over Alias and ScriptAlias directives, irrespective of their + ordering in the configuration file. Also, <em>URL-path</em> + must be an absolute path, not a relative path, even when used + with .htaccess files or inside of <Directory> + sections.</p> + + <p>If no <em>status</em> argument is given, the redirect will + be "temporary" (HTTP status 302). This indicates to the client + that the resource has moved temporarily. The <em>status</em> + argument can be used to return other HTTP status codes:</p> + + <dl> + <dt>permanent</dt> + + <dd>Returns a permanent redirect status (301) indicating that + the resource has moved permanently.</dd> + + <dt>temp</dt> + + <dd>Returns a temporary redirect status (302). This is the + default.</dd> + + <dt>seeother</dt> + + <dd>Returns a "See Other" status (303) indicating that the + resource has been replaced.</dd> + + <dt>gone</dt> + + <dd>Returns a "Gone" status (410) indicating that the + resource has been permanently removed. When this status is + used the <em>url</em> argument should be omitted.</dd> + </dl> + + <p>Other status codes can be returned by giving the numeric + status code as the value of <em>status</em>. If the status is + between 300 and 399, the <em>url</em> argument must be present, + otherwise it must be omitted. Note that the status must be + known to the Apache code (see the function + <code>send_error_response</code> in http_protocol.c).</p> + + <p>Example:</p> + + <pre> + Redirect permanent /one http://example.com/two<br /> + Redirect 303 /two http://example.com/other + </pre> + <hr /> + + <h2><a id="redirectmatch" + name="redirectmatch">RedirectMatch</a></h2> + + <p><a href="directive-dict.html#Syntax" + rel="Help"><strong>Syntax:</strong></a> RedirectMatch + [<em>status</em>] <em>regex URL</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>Context:</strong></a> server config, virtual + host, directory, .htaccess<br /> + <a href="directive-dict.html#Override" + rel="Help"><strong>Override:</strong></a> FileInfo<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>Status:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>Module:</strong></a> mod_alias<br /> + <a href="directive-dict.html#Compatibility" + rel="Help"><strong>Compatibility:</strong></a> Available in + Apache 1.3 and later</p> + + <p>This directive is equivalent to <a + href="#redirect">Redirect</a>, but makes use of standard + regular expressions, instead of simple prefix matching. The + supplied regular expression is matched against the URL-path, + and if it matches, the server will substitute any parenthesized + matches into the given string and use it as a filename. For + example, to redirect all GIF files to like-named JPEG files on + another server, one might use:</p> +<pre> + RedirectMatch (.*)\.gif$ http://www.anotherserver.com$1.jpg +</pre> + <hr /> + + <h2><a id="redirecttemp" name="redirecttemp">RedirectTemp + directive</a></h2> + + <p> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>Syntax:</strong></a> RedirectTemp + <em>URL-path URL</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>Context:</strong></a> server config, virtual + host, directory, .htaccess<br /> + <a href="directive-dict.html#Override" + rel="Help"><strong>Override:</strong></a> FileInfo<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>Status:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>Module:</strong></a> mod_alias<br /> + <a href="directive-dict.html#Compatibility" + rel="Help"><strong>Compatibility:</strong></a> This directive + is only available in Apache 1.2 and later</p> + + <p>This directive makes the client know that the Redirect is + only temporary (status 302). Exactly equivalent to + <code>Redirect temp</code>.</p> + <hr /> + + <h2><a id="redirectperm" name="redirectperm">RedirectPermanent + directive</a></h2> + + <p> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>Syntax:</strong></a> RedirectPermanent + <em>URL-path URL</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>Context:</strong></a> server config, virtual + host, directory, .htaccess<br /> + <a href="directive-dict.html#Override" + rel="Help"><strong>Override:</strong></a> FileInfo<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>Status:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>Module:</strong></a> mod_alias<br /> + <a href="directive-dict.html#Compatibility" + rel="Help"><strong>Compatibility:</strong></a> This directive + is only available in Apache 1.2 and later</p> + + <p>This directive makes the client know that the Redirect is + permanent (status 301). Exactly equivalent to <code>Redirect + permanent</code>.</p> + <hr /> + + <h2><a id="scriptalias" name="scriptalias">ScriptAlias + directive</a></h2> + + <p> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>Syntax:</strong></a> ScriptAlias + <em>URL-path file-path</em>|<em>directory-path</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>Context:</strong></a> server config, virtual + host<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>Status:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>Module:</strong></a> mod_alias</p> + + <p>The ScriptAlias directive has the same behavior as the <a + href="#alias">Alias</a> directive, except that in addition it + marks the target directory as containing CGI scripts that will be + processed by <a href="mod_cgi.html">mod_cgi</a>'s cgi-script + handler. URLs with a (%-decoded) path beginning with + <em>URL-path</em> will be mapped to scripts beginning with the + second argument which is a full pathname in the local + filesystem.</p> + + <p>Example:</p> + + <blockquote> + <code>ScriptAlias /cgi-bin/ /web/cgi-bin/</code> + </blockquote> + + <p>A request for http://myserver/cgi-bin/foo would cause the + server to run the script /web/cgi-bin/foo.</p> + <hr /> + + <h2><a id="scriptaliasmatch" + name="scriptaliasmatch">ScriptAliasMatch</a></h2> + + <p><a href="directive-dict.html#Syntax" + rel="Help"><strong>Syntax:</strong></a> ScriptAliasMatch + <em>regex file-path</em>|<em>directory-path</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>Context:</strong></a> server config, virtual + host<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>Status:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>Module:</strong></a> mod_alias<br /> + <a href="directive-dict.html#Compatibility" + rel="Help"><strong>Compatibility:</strong></a> Available in + Apache 1.3 and later</p> + + <p>This directive is equivalent to <a + href="#scriptalias">ScriptAlias</a>, but makes use of standard + regular expressions, instead of simple prefix matching. The + supplied regular expression is matched against the URL-path, + and if it matches, the server will substitute any parenthesized + matches into the given string and use it as a filename. For + example, to activate the standard <code>/cgi-bin</code>, one + might use:</p> +<pre> + ScriptAliasMatch ^/cgi-bin(.*) /usr/local/apache/cgi-bin$1 +</pre> + <hr /> + + <h3 align="CENTER">Apache HTTP Server Version 1.3</h3> + <a href="./"><img src="../images/index.gif" alt="Index" /></a> + <a href="../"><img src="../images/home.gif" alt="Home" /></a> + + </body> +</html> + diff --git a/usr.sbin/httpd/htdocs/manual/mod/mod_alias.html.ja.jis b/usr.sbin/httpd/htdocs/manual/mod/mod_alias.html.ja.jis new file mode 100644 index 00000000000..627a35c42b5 --- /dev/null +++ b/usr.sbin/httpd/htdocs/manual/mod/mod_alias.html.ja.jis @@ -0,0 +1,397 @@ +<?xml version="1.0" encoding="iso-2022-jp"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + + <title>Apache module mod_alias</title> + + </head> + <!-- English revision: 1.35 --> + <!-- Background white, links blue (unvisited), navy (visited), red (active) --> + <body bgcolor="#ffffff" text="#000000" link="#0000ff" + vlink="#000080" alink="#ff0000"> + <div align="CENTER"> + <img src="../images/sub.gif" alt="[APACHE DOCUMENTATION]" /> + + <h3>Apache HTTP Server Version 1.3</h3> + </div> + + + <h1 align="center">mod_alias $B%b%8%e!<%k(B</h1> + + <p>$B$3$N%b%8%e!<%k$O!"%[%9%H%U%!%$%k%7%9%F%`>e$N$$$m$$$m$J0c$&>l=j$r(B + $B%I%-%e%a%s%H%D%j!<$K%^%C%W$9$k5!G=$H!"(B + URL $B$N%j%@%$%l%/%H$r9T$J$&5!G=$rDs6!$7$^$9!#(B</p> + + <p><a href="module-dict.html#Status" + rel="Help"><strong>$B%9%F!<%?%9(B:</strong></a> Base<br /> + <a href="module-dict.html#SourceFile" + rel="Help"><strong>$B%=!<%9%U%!%$%k(B:</strong></a> mod_alias.c<br /> + <a href="module-dict.html#ModuleIdentifier" + rel="Help"><strong>$B%b%8%e!<%k<1JL;R(B:</strong></a> + alias_module</p> + + <h2>$B35MW(B</h2> + + <p>$B$3$N%b%8%e!<%k$N%G%#%l%/%F%#%V$O%5!<%P$K%j%/%(%9%H$,E~Ce$7$?$H$-$K(B + URL $B$NA`:n$d@)8f$r$9$k$3$H$r2DG=$K$7$^$9!#(B<code>Alias</code> + $B%G%#%l%/%F%#%V$H(B <code>ScriptAlias</code> $B%G%#%l%/%F%#%V$O(B + URL $B$H%U%!%$%k%7%9%F%`$N%Q%9$r%^%C%W$9$k$?$a$K;HMQ$5$l$^$9!#$3$l$O(B + <a href="core.html#documentroot"><code>DocumentRoot</code></a> + $B$N2<$K$J$$%I%-%e%a%s%H$r%&%'%V$N%I%-%e%a%s%H%D%j!<$N0lIt$H$7$F(B + $BAw$i$l$k$h$&$K$7$^$9!#(B<code>ScriptAlias</code> + $B%G%#%l%/%F%#%V$K$O%^%C%W@h$N%G%#%l%/%H%j$,(B CGI + $B%9%/%j%W%H$N$_$G$"$k$3$H$r<($9$H$$$&DI2C$N8z2L$,$"$j$^$9!#(B + </p> + + <p><code>Redirect</code> $B%G%#%l%/%F%#%V$O%/%i%$%"%s%H$K0c$C$?(B + URL $B$K?7$7$$%j%/%(%9%H$rAw$k$h$&$K;X<($7$^$9!#$3$l$O!"(B + $B%j%=!<%9$,?7$7$$>l=j$K0\F0$7$?$H$-$K$h$/;HMQ$5$l$^$9!#(B</p> + + <p>URL $B$rA`:n$9$k$?$a$N$h$j6/NO$G=@Fp$J%G%#%l%/%F%#%V72$O(B <a + href="mod_rewrite.html"><code>mod_rewrite</code></a> + $B%b%8%e!<%k$K$"$j$^$9!#(B + </p> + + <h2>$B%G%#%l%/%F%#%V(B</h2> + + <ul> + <li><a href="#alias">Alias</a></li> + + <li><a href="#aliasmatch">AliasMatch</a></li> + + <li><a href="#redirect">Redirect</a></li> + + <li><a href="#redirectmatch">RedirectMatch</a></li> + + <li><a href="#redirecttemp">RedirectTemp</a></li> + + <li><a href="#redirectperm">RedirectPermanent</a></li> + + <li><a href="#scriptalias">ScriptAlias</a></li> + + <li><a href="#scriptaliasmatch">ScriptAliasMatch</a></li> + </ul> + <hr /> + + <h2><a id="alias" name="alias">Alias $B%G%#%l%/%F%#%V(B</a></h2> + + <p> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>$B9=J8(B:</strong></a> Alias <em>URL-path + file-path</em>|<em>directory-path</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>$B%3%s%F%-%9%H(B:</strong></a> + $B%5!<%P@_Dj%U%!%$%k!"%P!<%A%c%k%[%9%H(B<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>$B%9%F!<%?%9(B:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>$B%b%8%e!<%k(B:</strong></a> mod_alias</p> + + <p>Alias $B%G%#%l%/%F%#%V$O%I%-%e%a%s%H$r%m!<%+%k%U%!%$%k%7%9%F%`$N(B + <a href="core.html#documentroot">DocumentRoot</a> + $B0J30$N>l=j$KJ]4I$9$k$3$H$r2DG=$K$7$^$9!#(B<em>Url-path</em> + (% $B$,I|9f$5$l$?(B) $B$G;O$^$k%Q%9$N(B URL $B$O(B + <em>directory-filename</em> + $B$G;O$^$k%m!<%+%k%U%!%$%k$K%^%C%W$5$l$^$9!#(B</p> + + <p>$BNc(B:</p> + + <blockquote> + <code>Alias /image /ftp/pub/image</code> + </blockquote> + + <p>http://myserver/image/foo.gif $B$X$N%j%/%(%9%H$KBP$7$F!"%5!<%P$O(B + $B%U%!%$%k(B /ftp/pub/image/foo.gif $B$rJV$7$^$9!#(B</p> + + <p>$B$b$7(B <em>url-path</em> $B$N:G8e$K(B / + $B$r=q$$$?$J$i!"%5!<%P$O%(%$%j%"%9$rE83+$9$k$?$a$K:G8e$N(B / + $B$rMW5a$9$k$H$$$&$3$H$KCm0U$7$F$/$@$5$$!#$9$J$o$A!"(B<code>Alias /icons/ + /usr/local/apache/icons/</code> $B$H$$$&$b$N$r;HMQ$7$F$$$k$H!"(B + <code>/icons</code> $B$H$$$&(B url $B$O%(%$%j%"%9$5$l$^$;$s!#(B</p> + + <p>$B%(%$%j%"%9$N(B<em>$B9T$-@h(B</em>$B$r4^$s$G$$$k(B <a + href="core.html#directory"><code><Directory></code></a> + $B%;%/%7%g%s$rDI2C$9$kI,MW$,$"$k$+$b$7$l$J$$$3$H$KCm0U$7$F$/$@$5$$!#(B + $B%(%$%j%"%9$NE83+$O(B <code><Directory></code> + $B%;%/%7%g%s$rD4$Y$kA0$K9T$J$o$l$^$9$N$G!"(B + $B%(%$%j%"%9$N9T$-@h$N(B <code><Directory></code> $B%;%/%7%g%s$N$_(B + $B8z2L$,$"$j$^$9!#(B + ($B$7$+$7!"(B<a + href="core.html#location"><code><Location></code></a> + $B%;%/%7%g%s$O%(%$%j%"%9$,=hM}$5$l$kA0$K<B9T$5$l$^$9$N$G!"(B + $B$3$A$i$OE,MQ$5$l$^$9!#(B)</p> + + <p><a href="#scriptalias">ScriptAlias</a> + $B$b;2>H$7$F$/$@$5$$!#(B</p> + <hr /> + + <h2><a id="aliasmatch" name="aliasmatch">AliasMatch</a></h2> + + <p><a href="directive-dict.html#Syntax" + rel="Help"><strong>$B9=J8(B:</strong></a> AliasMatch <em>regex + file-path</em>|<em>directory-path</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>$B%3%s%F%-%9%H(B:</strong></a> + $B%5!<%P@_Dj%U%!%$%k!"%P!<%A%c%k%[%9%H(B<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>$B%9%F!<%?%9(B:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>$B%b%8%e!<%k(B:</strong></a> mod_alias<br /> + <a href="directive-dict.html#Compatibility" + rel="Help"><strong>$B8_49@-(B:</strong></a> Apache 1.3 + $B0J9_$G;HMQ2DG=(B</p> + <p>$B$3$N%G%#%l%/%F%#%V$O(B <a href="#alias">Alias</a> + $B$H$[$H$s$IF1$8$G$9$,!"4JC1$J@hF,$+$i$N%^%C%A$r9T$J$&$N$G$O$J$/!"(B + $BI8=`@55,I=8=$rMxMQ$7$^$9!#$3$3$G;XDj$5$l$?@55,I=8=$H(B URL-path + $B$,9g$&$+$I$&$+$rD4$Y!"9g$&>l9g$O3g8L$G3g$i$l$?%^%C%A$r(B + $BM?$($i$l$?J8;zNs$GCV$-49$(!"$=$l$r%U%!%$%kL>$H$7$F;HMQ$7$^$9!#$?$H$($P!"(B + <code>/icons</code> $B%G%#%l%/%H%j$r;HMQ$9$k$h$&$K$9$k(B + $B$?$a$K$O0J2<$N$h$&$J$b$N$,;HMQ$G$-$^$9(B:</p> +<pre> + AliasMatch ^/icons(.*) /usr/local/apache/icons$1 +</pre> + <hr /> + + <h2><a id="redirect" name="redirect">Redirect + $B%G%#%l%/%F%#%V(B</a></h2> + + <p> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>$B9=J8(B:</strong></a> Redirect [<em>status</em>] + <em>URL-path URL</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>$B%3%s%F%-%9%H(B:</strong></a> + $B%5!<%P@_Dj%U%!%$%k!"%P!<%A%c%k%[%9%H!"(B + $B%G%#%l%/%H%j!"(B.htaccess<br /> + <a href="directive-dict.html#Override" + rel="Help"><strong>$B>e=q$-(B:</strong></a> FileInfo<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>$B%9%F!<%?%9(B:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>$B%b%8%e!<%k(B:</strong></a> mod_alias<br /> + <a href="directive-dict.html#Compatibility" + rel="Help"><strong>$B8_49@-(B:</strong></a> $B%G%#%l%/%H%j$H(B + .htaccess $B$N%3%s%F%-%9%H$O(B 1.1 $B0J9_$N$_!#(B<em>Status</em> + $B0z?t$O(B Apache 1.2 $B0J9_!#(B</p> + + <p>Redirect $B%G%#%l%/%F%#%V$O8E$$(B URL $B$r?7$7$$$b$N$X%^%C%W$7$^$9!#(B + $B?7$7$$(B URL $B$,%/%i%$%"%s%H$KJV$5$l$^$9!#$=$7$F!"(B + $B%/%i%$%"%s%H$O?7$7$$%"%I%l%9$r$b$&0l2s<hF@$7$h$&$H$7$^$9!#(B + <em>URL-path</em> (% $B$,I|9f$5$l$?(B) $B%Q%9$G;O$^$k%I%-%e%a%s%H$X$N(B + $B$9$Y$F$N%j%/%(%9%H$O(B <em>URL</em> $B$G;O$^$k?7$7$$(B + (% $B$,Id9f2=$5$l$?(B) URL $B$X$N%j%@%$%l%/%H%(%i!<$,JV$5$l$^$9!#(B</p> + + <p>$BNc(B:</p> + + <blockquote> + <code>Redirect /service http://foo2.bar.com/service</code> + </blockquote> + + <p>$B%/%i%$%"%s%H$O(B http://myserver/service/foo.txt + $B$X$N%j%/%(%9%H$r9T$J$&$H!"Be$o$j$K(B http://foo2.bar.com/service/foo.txt + $B$r%"%/%;%9$9$k$h$&$K9p$2$i$l$^$9!#(B</p> + + <p><strong>$BCm0U(B:</strong> + $B@_Dj%U%!%$%kCf$N=gHV$K4X$o$i$:!"(BRedirect $B%G%#%l%/%F%#%V$O(B Alias + $B%G%#%l%/%F%#%V$H(B ScriptAlias $B%G%#%l%/%F%#%V$h$j$bM%@h$5$l$^$9!#(B + $B$^$?!"(B.htaccess $B%U%!%$%k$d(B <Directory> + $B%;%/%7%g%s$NCf$G;H$o$l$F$$$?$H$7$F$b!"(B<em>URL-path</em> + $B$OAjBP%Q%9$G$O$J$/!"@dBP%Q%9$G$J$1$l$P$J$j$^$;$s!#(B</p> + + <p>$B$b$7(B <em>status</em> $B0z?t$,M?$($i$l$F$$$J$1$l$P!"%j%@%$%l%/%H$O(B + "temporary" (HTTP $B%9%F!<%?%9(B 302) $B$K$J$j$^$9!#$3$l$O%/%i%$%"%s%H$K(B + $B%j%=!<%9$,0l;~E*$K0\F0$7$?$H$$$&$3$H$r<($7$^$9!#(B<em>Status</em> + $B0z?t$O(B $BB>$N(B HTTP $B$N%9%F!<%?%9%3!<%I$rJV$9$?$a$K;HMQ$9$k$3$H$,$G$-$^$9(B:</p> + + <dl> + <dt>permanent</dt> + + <dd>$B1J5W$K%j%@%$%l%/%H$r$9$k%9%F!<%?%9(B (301) $B$rJV$7$^$9!#(B + $B$3$l$O%j%=!<%9$,1J5W$K0\F0$7$?$H$$$&$3$H$r0UL#$7$^$9!#(B</dd> + + <dt>temp</dt> + + <dd>$B0l;~E*$J%j%@%$%l%/%H%9%F!<%?%9(B (302) + $B$rJV$7$^$9!#$3$l$,%G%U%)%k%H$G$9!#(B</dd> + + <dt>seeother</dt> + + <dd>"See Other" $B%9%F!<%?%9(B (303) $B$rJV$7$^$9!#(B + $B$3$l$O%j%=!<%9$,B>$N$b$N$GCV$-49$($i$l$?$3$H$r0UL#$7$^$9!#(B</dd> + + <dt>gone</dt> + + <dd>"Gone" $B%9%F!<%?%9(B (410) $B$rJV$7$^$9!#$3$l$O%j%=!<%9$,1J5W$K(B + $B:o=|$5$l$?$3$H$r0UL#$7$^$9!#$3$N%9%F!<%?%9$,;HMQ$5$l$?>l9g!"(B + <em>url</em> $B0z?t$O>JN,$5$l$J$1$l$P$J$j$^$;$s!#(B</dd> + </dl> + + <p><em>Status</em> $B$NCM$K%9%F!<%?%9%3!<%I$r?tCM$GM?$($k$3$H$G(B + $BB>$N%9%F!<%?%9%3!<%I$bJV$9$3$H$,$G$-$^$9!#%9%F!<%?%9$,(B 300 $B$H(B 399 + $B$N4V$K$"$k>l9g!"(B<em>url</em> $B0z?t$OB8:_$7$F$$$J$1$l$P$$$1$^$;$s!#(B + $B$=$NB>$N>l9g$O>JN,$5$l$F$$$J$1$l$P$J$j$^$;$s!#$?$@$7!"(B + $B%9%F!<%?%9$O(B Apache $B$N%3!<%I$,CN$C$F$$$k$b$N$G$"$kI,MW$,$"$j$^$9(B + (http_protocol.c $B$N4X?t(B <code>send_error_response</code> + $B$r8+$F$/$@$5$$(B)$B!#(B</p> + <p>$BNc(B:</p> + + <pre> + Redirect permanent /one http://example.com/two<br /> + Redirect 303 /two http://example.com/other + </pre> + <hr /> + + <h2><a id="redirectmatch" + name="redirectmatch">RedirectMatch</a></h2> + + <p><a href="directive-dict.html#Syntax" + rel="Help"><strong>$B9=J8(B:</strong></a> RedirectMatch + [<em>status</em>] <em>regex URL</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>$B%3%s%F%-%9%H(B:</strong></a> $B%5!<%P@_Dj%U%!%$%k!"(B + $B%P!<%A%c%k%[%9%H!"%G%#%l%/%H%j!"(B.htaccess<br /> + <a href="directive-dict.html#Override" + rel="Help"><strong>$B>e=q$-(B:</strong></a> FileInfo<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>$B%9%F!<%?%9(B:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>$B%b%8%e!<%k(B:</strong></a> mod_alias<br /> + <a href="directive-dict.html#Compatibility" + rel="Help"><strong>$B8_49@-(B:</strong></a> Apache 1.3 + $B0J9_$G;HMQ2DG=!#(B</p> + + <p>$B$3$N%G%#%l%/%F%#%V$O(B <a href="#redirect">Redirect</a> + $B$H$[$H$s$IF1$8$G$9$,!"4JC1$J@hF,$+$i$N%^%C%A$r9T$J$&$N$G$O$J$/!"(B + $BI8=`@55,I=8=$rMxMQ$7$^$9!#$3$3$G;XDj$5$l$?@55,I=8=$H(B URL-path + $B$,9g$&$+$I$&$+$rD4$Y!"9g$&>l9g$O3g8L$G3g$i$l$?%^%C%A$r(B + $BM?$($i$l$?J8;zNs$GCV$-49$(!"$=$l$r%U%!%$%kL>$H$7$F;HMQ$7$^$9!#(B + $B$?$H$($P!"$9$Y$F$N(B GIF $B%U%!%$%k$rJL%5!<%P$NF1MM$JL>A0$N(B JPEG + $B%U%!%$%k$K%j%@%$%l%/%H$9$k$K$O!"0J2<$N$h$&$J$b$N$r;H$$$^$9(B: + </p> +<pre> + RedirectMatch (.*)\.gif$ http://www.anotherserver.com$1.jpg +</pre> + <hr /> + + <h2><a id="redirecttemp" name="redirecttemp">RedirectTemp + $B%G%#%l%/%F%#%V(B</a></h2> + + <p> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>$B9=J8(B:</strong></a> RedirectTemp <em>URL-path + URL</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>$B%3%s%F%-%9%H(B:</strong></a> $B%5!<%P@_Dj%U%!%$%k!"(B + $B%P!<%A%c%k%[%9%H!"%G%#%l%/%H%j!"(B.htaccess<br /> + <a href="directive-dict.html#Override" + rel="Help"><strong>$B>e=q$-(B:</strong></a> FileInfo<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>$B%9%F!<%?%9(B:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>$B%b%8%e!<%k(B:</strong></a> mod_alias<br /> + <a href="directive-dict.html#Compatibility" + rel="Help"><strong>$B8_49@-(B:</strong></a> + $B$3$N%G%#%l%/%F%#%V$O(B Apache 1.2 $B0J9_$G$N$_;HMQ2DG=(B</p> + + <p>$B$3$N%G%#%l%/%F%#%V$O%/%i%$%"%s%H$K(B Redirect + $B$,0l;~E*$J$b$N$G$"$k(B ($B%9%F!<%?%9(B 302) $B$3$H$rCN$i$;$^$9!#(B + <code>Redirect temp</code> $B$H$^$C$?$/F1$8$G$9!#(B</p> + <hr /> + + <h2><a id="redirectperm" name="redirectperm">RedirectPermanent + $B%G%#%l%/%F%#%V(B</a></h2> + + <p> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>$B9=J8(B:</strong></a> RedirectPermanent + <em>URL-path URL</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>$B%3%s%F%-%9%H(B:</strong></a> $B%5!<%P@_Dj%U%!%$%k!"(B + $B%P!<%A%c%k%[%9%H!"%G%#%l%/%H%j!"(B.htaccess<br /> + <a href="directive-dict.html#Override" + rel="Help"><strong>$B>e=q$-(B:</strong></a> FileInfo<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>$B%9%F!<%?%9(B:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>$B%b%8%e!<%k(B:</strong></a> mod_alias<br /> + <a href="directive-dict.html#Compatibility" + rel="Help"><strong>$B8_49@-(B:</strong></a> + $B$3$N%G%#%l%/%F%#%V$O(B Apache 1.2 $B0J9_$G$N$_;HMQ2DG=!#(B</p> + + <p>$B$3$N%G%#%l%/%F%#%V$O%/%i%$%"%s%H$K(B Redirect $B$,1J5WE*$J$b$N(B + ($B%9%F!<%?%9(B 301) $B$G$"$k$3$H$rCN$i$;$^$9!#(B + <code>Redirect premanent</code> $B$H$^$C$?$/F1$8$G$9!#(B</p> + <hr /> + + <h2><a id="scriptalias" name="scriptalias">ScriptAlias + $B%G%#%l%/%F%#%V(B</a></h2> + + <p> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>$B9=J8(B:</strong></a> ScriptAlias <em>URL-path + file-path</em>|<em>directory-path</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>$B%3%s%F%-%9%H(B:</strong></a> + $B%5!<%P@_Dj%U%!%$%k!"%P!<%A%c%k%[%9%H(B<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>$B%9%F!<%?%9(B:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>$B%b%8%e!<%k(B:</strong></a> mod_alias</p> + + <p>ScriptAlias $B%G%#%l%/%F%#%V$O!"BP>]%G%#%l%/%H%j$K(B + <a href="mod_cgi.html">mod_cgi</a> $B$N(B cgi-script + $B%O%s%I%i$G=hM}$5$l$k(B CGI + $B%9%/%j%W%H$,$"$k$3$H$r<($90J30$O(B + <a href="#alias">Alias</a> + $B%G%#%l%/%F%#%V$HF1$8?6$kIq$$$r$7$^$9!#(B<em>URL-path</em> + (% $B$,I|9f$5$l$?(B) $B%Q%9$G(B $B;O$^$k(B URL $B$O%m!<%+%k$N%U%!%$%k%7%9%F%`$N(B + $B%U%k%Q%9$G$"$kFsHVL\$N0z?t$K%^%C%W$5$l$^$9!#(B</p> + + <p>$BNc(B:</p> + + <blockquote> + <code>ScriptAlias /cgi-bin/ /web/cgi-bin/</code> + </blockquote> + + <p>http://myserver/cgi-bin/foo $B$X$N%j%/%(%9%H$KBP$7$F%5!<%P$O%9%/%j%W%H(B + /web/cgi-bin/foo $B$r<B9T$7$^$9!#(B</p> + <hr /> + + <h2><a id="scriptaliasmatch" + name="scriptaliasmatch">ScriptAliasMatch</a></h2> + + <p><a href="directive-dict.html#Syntax" + rel="Help"><strong>$B9=J8(B:</strong></a> ScriptAliasMatch <em>regex + file-path</em>|<em>directory-path</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>$B%3%s%F%-%9%H(B:</strong></a> + $B%5!<%P@_Dj%U%!%$%k!"%P!<%A%c%k%[%9%H(B<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>$B%9%F!<%?%9(B:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>$B%b%8%e!<%k(B:</strong></a> mod_alias<br /> + <a href="directive-dict.html#Compatibility" + rel="Help"><strong>$B8_49@-(B:</strong></a> Apache 1.3 + $B0J9_$G;HMQ2DG=(B</p> + + <p>$B$3$N%G%#%l%/%F%#%V$O(B <a href="#scriptalias">ScriptAlias</a> + $B$H$[$H$s$IF1$8$G$9$,!"4JC1$J@hF,$+$i$N%^%C%A$r9T$J$&$N$G$O$J$/!"(B + $BI8=`@55,I=8=$rMxMQ$7$^$9!#$3$3$G;XDj$5$l$?@55,I=8=$H(B URL-path + $B$,9g$&$+$I$&$+$rD4$Y!"9g$&>l9g$O3g8L$G3g$i$l$?%^%C%A$r(B + $BM?$($i$l$?J8;zNs$GCV$-49$(!"$=$l$r%U%!%$%kL>$H$7$F;HMQ$7$^$9!#(B + $B$?$H$($P!"I8=`$N(B <code>/cgi-bin</code> + $B$r;HMQ$9$k$h$&$K$9$k$?$a$K$O!"0J2<$N$h$&$J$b$N$r;H$$$^$9(B: + </p> +<pre> + ScriptAliasMatch ^/cgi-bin(.*) /usr/local/apache/cgi-bin$1 +</pre> + <hr /> + + <h3 align="CENTER">Apache HTTP Server Version 1.3</h3> + <a href="./"><img src="../images/index.gif" alt="Index" /></a> + <a href="../"><img src="../images/home.gif" alt="Home" /></a> + + </body> +</html> diff --git a/usr.sbin/httpd/htdocs/manual/mod/mod_auth.html.en b/usr.sbin/httpd/htdocs/manual/mod/mod_auth.html.en new file mode 100644 index 00000000000..7fabe112cfa --- /dev/null +++ b/usr.sbin/httpd/htdocs/manual/mod/mod_auth.html.en @@ -0,0 +1,322 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta name="generator" content="HTML Tidy, see www.w3.org" /> + + <title>Apache module mod_auth</title> + </head> + <!-- Background white, links blue (unvisited), navy (visited), red (active) --> + + <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" + vlink="#000080" alink="#FF0000"> + <div align="CENTER"> + <img src="../images/sub.gif" alt="[APACHE DOCUMENTATION]" /> + + <h3>Apache HTTP Server Version 1.3</h3> + </div> + + + <h1 align="CENTER">Module mod_auth</h1> + + <p>This module provides for user authentication using text + files.</p> + + <p><a href="module-dict.html#Status" + rel="Help"><strong>Status:</strong></a> Base<br /> + <a href="module-dict.html#SourceFile" + rel="Help"><strong>Source File:</strong></a> mod_auth.c<br /> + <a href="module-dict.html#ModuleIdentifier" + rel="Help"><strong>Module Identifier:</strong></a> + auth_module</p> + + <h2>Summary</h2> + + <p>This module allows the use of HTTP Basic Authentication to + restrict access by looking up users in plain text password and + group files. Similar functionality and greater scalability is + provided by <a href="mod_auth_dbm.html">mod_auth_dbm</a> and <a + href="mod_auth_db.html">mod_auth_db</a>. HTTP Digest + Authentication is provided by <a + href="mod_auth_digest.html">mod_auth_digest</a>.</p> + + <p><b>Note that these credential-based security mechanisms are + only as strong as your Web server's security. As a rule, they + are <i>not</i> as strong as the operating system's own security + system.</b></p> + + <h2>Directives</h2> + + <ul> + <li><a href="#authgroupfile">AuthGroupFile</a></li> + + <li><a href="#authuserfile">AuthUserFile</a></li> + + <li><a href="#authauthoritative">AuthAuthoritative</a></li> + </ul> + + <p>See also: <a href="core.html#require">require</a>, <a + href="core.html#satisfy">satisfy</a>, and <a + href="#require">mod_auth require keywords</a>.</p> + <hr /> + + <h2><a id="require" name="require"><code>mod_auth</code> + Require Keywords</a></h2> + + <p>The <code>mod_auth</code> module supports the following + keywords that can be given to the <a + href="core.html#require">Require</a> directive:</p> + + <dl compact="compact"> + <dt><code>user <i>username</i> [...]</code></dt> + + <dd>The supplied username and password must be in the <a + href="#authuserfile">AuthUserFile</a> database, and the + username must also be one of those listed on the Require + directive.</dd> + + <dt><code>group <i>groupname</i> [...]</code></dt> + + <dd>The supplied username and password must be in the <a + href="#authuserfile">AuthUserFile</a> database, and the + username must also be a member of one of the named groups in + the <a href="#authgroupfile">AuthGroupFile</a> database.</dd> + + <dt><code>valid-user</code></dt> + + <dd>The supplied username and password must be in the <a + href="#authuserfile">AuthUserFile</a> database. Any valid + username from that file will be allowed.</dd> + + <dt><code>file-owner</code></dt> + + <dd>[Available after Apache 1.3.20] The supplied username and + password must be in the <a + href="#authuserfile">AuthUserFile</a> database, and the + username must also match the system's name for the owner of + the file being requested. That is, if the operating system + say the requested file is owned by <code>jones</code>, then + the username used to access it through the Web must be + <code>jones</code> as well.</dd> + + <dt><code>file-group</code></dt> + + <dd>[Available after Apache 1.3.20] The supplied username and + password must be in the <a + href="#authuserfile">AuthUserFile</a> database, the name of + the group that owns the file must be in the <a + href="#authgroupfile">AuthGroupFile</a> database, and the + username must be a member of that group. For example, if the + operating system says the requested file is owned by group + <code>accounts</code>, the group <code>accounts</code> must + be in the AuthGroupFile database and the username used in the + request must be a member of that group.</dd> + </dl> + <hr /> + + <h2><a id="example" 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> + <Directory /home/*/public_html/private> + AuthType Basic + AuthName MyPrivateFile + AuthUserFile /usr/local/apache/etc/.htpasswd-allusers + Satisfy All + Require file-owner + </Directory> +</pre> + <hr /> + + <h2><a id="authgroupfile" + name="authgroupfile">AuthGroupFile</a> directive</h2> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>Syntax:</strong></a> AuthGroupFile + <em>file-path</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>Context:</strong></a> directory, + .htaccess<br /> + <a href="directive-dict.html#Override" + rel="Help"><strong>Override:</strong></a> AuthConfig<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>Status:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>Module:</strong></a> mod_auth + + <p>The AuthGroupFile directive sets the name of a textual file + containing the list of user groups for user authentication. + <em>File-path</em> is the path to the group file. If it is not + absolute (<em>i.e.</em>, if it doesn't begin with a slash), it + is treated as relative to the ServerRoot.</p> + + <p>Each line of the group file contains a groupname followed by + a colon, followed by the member usernames separated by spaces. + Example:</p> + + <blockquote> + <code>mygroup: bob joe anne</code> + </blockquote> + Note that searching large text files is <em>very</em> + inefficient; <a + href="mod_auth_dbm.html#authdbmgroupfile">AuthDBMGroupFile</a> + should be used instead. + + <p>Security: make sure that the AuthGroupFile is stored outside + the document tree of the web-server; do <em>not</em> put it in + the directory that it protects. Otherwise, clients will be able + to download the AuthGroupFile.</p> + + <p>See also <a href="core.html#authname">AuthName</a>, <a + href="core.html#authtype">AuthType</a> and <a + href="#authuserfile">AuthUserFile</a>.</p> + <hr /> + + <h2><a id="authuserfile" name="authuserfile">AuthUserFile</a> + directive</h2> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>Syntax:</strong></a> AuthUserFile + <em>file-path</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>Context:</strong></a> directory, + .htaccess<br /> + <a href="directive-dict.html#Override" + rel="Help"><strong>Override:</strong></a> AuthConfig<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>Status:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>Module:</strong></a> mod_auth + + <p>The AuthUserFile directive sets the name of a textual file + containing the list of users and passwords for user + authentication. <em>File-path</em> is the path to the user + file. If it is not absolute (<em>i.e.</em>, if it doesn't begin + with a slash), it is treated as relative to the ServerRoot.</p> + + <p>Each line of the user file contains a username followed by a + colon, followed by the <code>crypt()</code> encrypted password. + The behavior of multiple occurrences of the same user is + undefined.</p> + + <p>The utility <a href="../programs/htpasswd.html">htpasswd</a> + which is installed as part of the binary distribution, or which + can be found in <code>src/support</code>, is used to maintain + this password file. See the <code>man</code> page for more + details. In short</p> + + <blockquote> + <code>htpasswd -c Filename username</code><br /> + Create a password file 'Filename' with 'username' as the + initial ID. It will prompt for the password. <code>htpasswd + Filename username2</code><br /> + Adds or modifies in password file 'Filename' the 'username'. + </blockquote> + + <p>Note that searching large text files is <em>very</em> + inefficient; <a + href="mod_auth_dbm.html#authdbmuserfile">AuthDBMUserFile</a> + should be used instead.</p> + + <dl> + <dt><b>Security:</b></dt> + + <dd>Make sure that the AuthUserFile is stored outside the + document tree of the web-server; do <em>not</em> put it in + the directory that it protects. Otherwise, clients may be + able to download the AuthUserFile.</dd> + + <dd>Also be aware that null usernames are permitted, and null + passwords as well (through Apache 1.3.20). If your + AuthUserFile includes a line containing only a colon (':'), a + '<code>Require valid-user</code>' will allow access if both + the username and password in the credentials are + omitted.</dd> + </dl> + See also <a href="core.html#authname">AuthName</a>, <a + href="core.html#authtype">AuthType</a> and <a + href="#authgroupfile">AuthGroupFile</a>. + <hr /> + + <h2><a id="authauthoritative" + name="authauthoritative">AuthAuthoritative</a> directive</h2> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>Syntax:</strong></a> AuthAuthoritative + on|off<br /> + <a href="directive-dict.html#Default" + rel="Help"><strong>Default:</strong></a> + <code>AuthAuthoritative on</code><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>Context:</strong></a> directory, + .htaccess<br /> + <a href="directive-dict.html#Override" + rel="Help"><strong>Override:</strong></a> AuthConfig<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>Status:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>Module:</strong></a> mod_auth + + <p>Setting the AuthAuthoritative directive explicitly to + <strong>'off'</strong> allows for both authentication and + authorization to be passed on to lower level modules (as + defined in the <code>Configuration</code> and + <code>modules.c</code> files) if there is <strong>no + userID</strong> or <strong>rule</strong> matching the supplied + userID. If there is a userID and/or rule specified; the usual + password and access checks will be applied and a failure will + give an Authorization Required reply.</p> + + <p>So if a userID appears in the database of more than one + module; or if a valid <code>Require</code> directive applies to + more than one module; then the first module will verify the + credentials; and no access is passed on; regardless of the + AuthAuthoritative setting.</p> + + <p>A common use for this is in conjunction with one of the + database modules; such as <a + href="mod_auth_db.html"><code>mod_auth_db.c</code></a>, <a + href="mod_auth_dbm.html"><code>mod_auth_dbm.c</code></a>, + <code>mod_auth_msql.c</code>, and <a + href="mod_auth_anon.html"><code>mod_auth_anon.c</code></a>. + These modules supply the bulk of the user credential checking; + but a few (administrator) related accesses fall through to a + lower level with a well protected AuthUserFile.</p> + + <p><a href="directive-dict.html#Default" + rel="Help"><strong>Default:</strong></a> By default; control is + not passed on; and an unknown userID or rule will result in an + Authorization Required reply. Not setting it thus keeps the + system secure; and forces an NCSA compliant behavior.</p> + + <p>Security: Do consider the implications of allowing a user to + allow fall-through in his .htaccess file; and verify that this + is really what you want; Generally it is easier to just secure + a single .htpasswd file, than it is to secure a database such + as mSQL. Make sure that the AuthUserFile is stored outside the + document tree of the web-server; do <em>not</em> put it in the + directory that it protects. Otherwise, clients will be able to + download the AuthUserFile.</p> + + <p>See also <a href="core.html#authname">AuthName</a>, <a + href="core.html#authtype">AuthType</a> and <a + href="#authgroupfile">AuthGroupFile</a>.</p> + + <p> <hr /> + + <h3 align="CENTER">Apache HTTP Server Version 1.3</h3> + <a href="./"><img src="../images/index.gif" alt="Index" /></a> + <a href="../"><img src="../images/home.gif" alt="Home" /></a> + + </p> + </body> +</html> + diff --git a/usr.sbin/httpd/htdocs/manual/mod/mod_auth.html.ja.jis b/usr.sbin/httpd/htdocs/manual/mod/mod_auth.html.ja.jis new file mode 100644 index 00000000000..5188114dffa --- /dev/null +++ b/usr.sbin/httpd/htdocs/manual/mod/mod_auth.html.ja.jis @@ -0,0 +1,335 @@ +<?xml version="1.0" encoding="iso-2022-jp"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <title>Apache module mod_auth</title> + </head> + <!-- English revision: 1.29 --> + <!-- Background white, links blue (unvisited), navy (visited), red (active) --> + + <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#000080" + alink="#FF0000"> + <div align="CENTER"> + <img src="../images/sub.gif" alt="[APACHE DOCUMENTATION]" /> + + <h3>Apache HTTP Server Version 1.3</h3> + </div> + + + <h1 align="center">mod_auth $B%b%8%e!<%k(B</h1> + + <p> + $B$3$N%b%8%e!<%k$O%F%-%9%H%U%!%$%k$r;H$C$F%f!<%6$NG'>Z$r9T$J$&5!G=$r(B + $BDs6!$7$^$9!#(B</p> + + <p><a href="module-dict.html#Status" + rel="Help"><strong>$B%9%F!<%?%9(B:</strong></a> Base<br /> + <a href="module-dict.html#SourceFile" + rel="Help"><strong>$B%=!<%9%U%!%$%k(B:</strong></a> + mod_auth.c<br /> + <a href="module-dict.html#ModuleIdentifier" + rel="Help"><strong>$B%b%8%e!<%k<1JL;R(B:</strong></a> + auth_module</p> + + <h2>$B35MW(B</h2> + + <p> + $B$3$N%b%8%e!<%k$O%f!<%6$r%W%l!<%s%F%-%9%H$N%Q%9%o!<%I$H%0%k!<%W(B + $B%U%!%$%k$GD4$Y$k$3$H$K$h$j!"(BHTTP + $B4pK\G'>Z$G%"%/%;%9$r@)8B$9$k$3$H$r(B + $B2DG=$K$7$^$9!#F1MM$N5!G=$G%9%1!<%i%S%j%F%#$N$"$k$b$N$O(B <a + href="mod_auth_dbm.html">mod_auth_dbm</a> $B$H(B <a + href="mod_auth_db.html">mod_auth_db</a> $B$K$h$jDs6!$5$l$^$9!#(B + HTTP $B%@%$%8%'%9%HG'>Z$O(B <a + href="mod_auth_digest.html">mod_auth_digest</a> + $B$K$h$jDs6!$5$l$F$$$^$9!#(B</p> + + <p> + <b>$B$3$l$i$NG'>Z$K4p$E$$$?%;%-%e%j%F%#$N5!9=$O$;$$$<$$%&%'%V%5!<%P$N(B + $B%;%-%e%j%F%#$HF1DxEY$N6/EY$G$"$k$3$H$KCm0U$7$F$/$@$5$$!#(B + $B0lHL$K!"%*%Z%l!<%F%#%s%0%7%9%F%`$N%;%-%e%j%F%#%7%9%F%`$[$I$O(B + $B6/$/(B<i>$B$"$j$^$;$s(B</i>$B!#(B</b></p> + + <h2>$B%G%#%l%/%F%#%V(B</h2> + + <ul> + <li><a href="#authgroupfile">AuthGroupFile</a></li> + + <li><a href="#authuserfile">AuthUserFile</a></li> + + <li><a href="#authauthoritative">AuthAuthoritative</a></li> + </ul> + + <p>$B;2>H(B: <a href="core.html#require">require</a>, <a + href="core.html#satisfy">satisfy</a>, <a href="#require">mod_auth + require $B%-!<%o!<%I(B</a>$B!#(B</p> + <hr /> + + <h2><a id="require" name="require"><code>mod_auth</code> Require + $B%-!<%o!<%I(B</a></h2> + + <p><code>mod_auth</code> $B%b%8%e!<%k$O(B <a + href="core.html#require">Require</a> $B%G%#%l%/%F%#%V$KBP$9$k(B + $B0J2<$N%-!<%o!<%I$r%5%]!<%H$7$^$9(B:</p> + + <dl compact="compact"> + <dt><code>user <i>username</i> [...]</code></dt> + + <dd>$BM?$($i$l$?%f!<%6L>$H%Q%9%o!<%I$O(B <a + href="#authuserfile">AuthUserFile</a> + $B%G!<%?%Y!<%9$KB8:_$9$k(B $BI,MW$,$"$j!"$5$i$K%f!<%6L>$,(B + Require $B%G%#%l%/%F%#%V$K%j%9%H(B + $B$5$l$F$$$kI,MW$,$"$j$^$9!#(B</dd> + + <dt><code>group <i>groupname</i> [...]</code></dt> + + <dd>$BM?$($i$l$?%f!<%6L>$H%Q%9%o!<%I$O(B <a + href="#authuserfile">AuthUserFile</a> + $B%G!<%?%Y!<%9$KB8:_$9$k(B $BI,MW$,$"$j!"$5$i$K%f!<%6L>$,(B + <a href="#authgroupfile">AuthGroupFile</a> + $B%G!<%?%Y!<%9$K$"$k(B + $B;XDj$5$l$?%0%k!<%W$N%a%s%P$G$"$kI,MW$,$"$j$^$9!#(B</dd> + + <dt><code>valid-user</code></dt> + + <dd>$BM?$($i$l$?%f!<%6L>$H%Q%9%o!<%I$,(B <a + href="#authuserfile">AuthUserFile</a> + $B%G!<%?%Y!<%9$KB8:_$9$k(B + $BI,MW$,$"$j$^$9!#$=$N%U%!%$%k$K$"$kM-8z$J%f!<%6L>$O%"%/%;%9$,5v2D(B + $B$5$l$^$9!#(B</dd> + + <dt><code>file-owner</code></dt> + + <dd>[Apache 1.3.20 $B$+$i(B] + $BM?$($i$l$?%f!<%6L>$H%Q%9%o!<%I$O(B <a + href="#authuserfile">AuthUserFile</a> + $B%G!<%?%Y!<%9$KB8:_$9$k(B + $BI,MW$,$"$j!"$5$i$K%f!<%6L>$,%j%/%(%9%H$5$l$?%U%!%$%k$N(B + $B%7%9%F%`$N=jM-<T$NL>A0$H0lCW$9$kI,MW$,$"$j$^$9!#$D$^$j!"(B + $B%*%Z%l!<%F%#%s%0%7%9%F%`$,%j%/%(%9%H$5$l$?%U%!%$%k$,(B + <code>jones</code> $B$G$"$k!"$H8@$C$?>l9g$O!"(BWeb + $B$rDL$7$F(B $B%"%/%;%9$9$k%f!<%6L>$b(B <code>jones</code> + $B$G$"$kI,MW$G$"$k!"(B $B$H$$$&$3$H$G$9!#(B</dd> + + <dt><code>file-group</code></dt> + + <dd>[Apache 1.3.20 $B$+$i(B] + $BM?$($i$l$?%f!<%6L>$H%Q%9%o!<%I$O(B <a + href="#authuserfile">AuthUserFile</a> + $B%G!<%?%Y!<%9$KB8:_$9$k(B + $BI,MW$,$"$j!"%U%!%$%k$r=jM-$9$k%0%k!<%WL>$,(B <a + href="#authgroupfile">AuthGroupFile</a> $B%G!<%?%Y!<%9$K(B + $B$"$kI,MW$,$"$j!"%f!<%6L>$,$=$N%0%k!<%W$N%a%s%P$G$"$kI,MW$,$"$j$^$9!#(B + $BNc$($P!"%*%Z%l!<%F%#%s%0%7%9%F%`$,%j%/%(%9%H$5$l$?%U%!%$%k$,(B + $B%0%k!<%W(B <code>accounts</code> + $B$K$h$j=jM-$5$l$F$$$k$H8@$C$?(B $B>l9g!"%0%k!<%W(B + <code>accounts</code> $B$,(B AuthGroupFile $B%G!<%?%Y!<%9$K(B + $BB0$7$F$$$kI,MW$,$"$j!"%j%/%(%9%H$K;HMQ$5$l$?%f!<%6L>$b(B + $B$=$N%0%k!<%W$N%a%s%P$G$"$kI,MW$,$"$j$^$9!#(B</dd> + </dl> + <hr /> + + <h2><a id="authgroupfile" name="authgroupfile">AuthGroupFile</a> + $B%G%#%l%/%F%#%V(B</h2> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>$B9=J8(B:</strong></a> AuthGroupFile + <em>filename</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>$B%3%s%F%-%9%H(B:</strong></a> + $B%G%#%l%/%H%j!"(B.htaccess<br /> + <a href="directive-dict.html#Override" + rel="Help"><strong>$B>e=q$-(B:</strong></a> AuthConfig<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>$B%9%F!<%?%9(B:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>$B%b%8%e!<%k(B:</strong></a> mod_auth + + <p>AuthGroupFile $B%G%#%l%/%F%#%V$O%f!<%6G'>Z$N$?$a$N(B + $B%f!<%6%0%k!<%W$N%j%9%H$,=q$+$l$?%F%-%9%H%U%!%$%k$NL>A0$r@_Dj$7$^$9!#(B + <em>Filename</em> + $B$O%0%k!<%W%U%!%$%k$N%Q%9$G$9!#@dBP%Q%9$G$J$$$H$-$O(B + (<em>$B$9$J$o$A(B</em>$B!"%9%i%C%7%e$G;O$^$i$J$$$H$-$O(B)$B!"(BServerRoot + $B$+$i$NAjBP%Q%9$H$7$F07$o$l$^$9!#(B</p> + + <p> + $B%0%k!<%W%U%!%$%k$N$=$l$>$l$N9T$O!"%0%k!<%WL>!"%3%m%s!"6uGr$G(B + $B6h@Z$i$l$?%0%k!<%W$KB0$9$k%f!<%6L>!"$+$i$J$j$^$9!#Nc(B:</p> + + <blockquote> + <code>mygroup: bob joe anne</code> + </blockquote> + + <p> + $BBg$-$J%F%-%9%H%U%!%$%k$rC5$9$N$O(B<em>$BHs>o(B</em>$B$K8zN($,0-$$$H$$$&$3$H$K(B + $BCm0U$7$F$/$@$5$$!#$=$N$h$&$J>l9g$O!"Be$o$j$K(B <a + href="mod_auth_dbm.html#authdbmgroupfile">AuthDBMGroupFile</a> + $B$r(B $B;H$C$F$/$@$5$$!#(B</p> + + <p>$B%;%-%e%j%F%#(B: AuthGroupFile + $B$OI,$:%&%'%V%5!<%P$N%I%-%e%a%s%H%D%j!<$N30$K(B + $BJ]4I$7$F$/$@$5$$!#$=$l$,J]8n$7$F$$$k%G%#%l%/%H%j$K$OCV$+(B<em>$B$J$$(B</em>$B$G(B + $B$/$@$5$$!#$=$&$G$J$$$H!"%/%i%$%"%s%H$,(B AuthGroupFile + $B$r%@%&%s%m!<%I(B $B$G$-$F$7$^$$$^$9!#(B</p> + + <p><a href="core.html#authname">AuthName</a>, <a + href="core.html#authtype">AuthType</a>, <a + href="#authuserfile">AuthUserFile</a> + $B$b;2>H$7$F$/$@$5$$!#(B</p> + <hr /> + + <h2><a id="authuserfile" name="authuserfile">AuthUserFile</a> + $B%G%#%l%/%F%#%V(B</h2> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>$B9=J8(B:</strong></a> AuthUserFile + <em>file-path</em><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>$B%3%s%F%-%9%H(B:</strong></a> + $B%G%#%l%/%H%j!"(B.htaccess<br /> + <a href="directive-dict.html#Override" + rel="Help"><strong>$B>e=q$-(B:</strong></a> AuthConfig<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>$B%9%F!<%?%9(B:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>$B%b%8%e!<%k(B:</strong></a> mod_auth<br /> + + + <p>AuthUserFile + $B%G%#%l%/%F%#%V$O%f!<%6G'>Z$N$?$a$N%f!<%6$H%Q%9%o!<%I$N(B + $B%j%9%H$,=q$+$l$?%F%-%9%H%U%!%$%k$rL>A0$r@_Dj$7$^$9!#(B<em>File-path</em> + $B$O(B $B%f!<%6%U%!%$%k$X$N%Q%9$G$9!#@dBP%Q%9$G$J$$$H$-$O(B + (<em>$B$9$J$o$A(B</em>$B!"(B + $B%9%i%C%7%e$G;O$^$i$J$$$H$-$O(B)$B!"(BServerRoot + $B$+$i$NAjBP%Q%9$H$7$F07$o$l$^$9!#(B</p> + + <p> + $B%f!<%6%U%!%$%k$N$=$l$>$l$N9T$O!"%f!<%6L>!"%3%m%s!"(B<code>crypt()</code> + $B$K$h$j0E9f2=$5$l$?(B + $B%Q%9%o!<%I!"$+$i$J$j$^$9!#F1$8%f!<%6$,J#?t2s8=$l$?$H$-$NF0:n$O(B + $BITDj$G$9!#(B</p> + + <p> + $B%P%$%J%jG[I[$N0lIt$H$7$F%$%s%9%H!<%k$5$l$F$$$k$+!"(B<code>src/support</code> + $B$K$"$k(B <a href="../programs/htpasswd.html">htpasswd</a> + $B%f!<%F%#%j%F%#$O!"(B + $B$3$N%Q%9%o!<%I%U%!%$%k$r0];}$9$k$?$a$K;HMQ$5$l$^$9!#>\:Y$O(B + <code>man</code> + $B%Z!<%8$r;2>H$7$F$/$@$5$$!#<jC;$+$K@bL@$9$k$H(B</p> + + <blockquote> + <code>htpasswd -c Filename username</code><br /> + $B$O(B 'username' $B$r=i4|(B ID $B$H$7$F%Q%9%o!<%I%U%!%$%k(B + 'Filename' $B$r(B + $B:n@.$7$^$9!#$3$l$O%Q%9%o!<%I$NF~NO$rB%$7$^$9!#(B <code>htpasswd + Filename username2</code><br /> + $B$O%Q%9%o!<%I%U%!%$%k(B 'Filename' $B$K(B 'username' $B$r(B + $BDI2C$9$k$+!"4{$K$"$k(B 'username' $B$r=$@5$7$^$9!#(B + </blockquote> + + <p> + $BBg$-$J%F%-%9%H%U%!%$%k$rC5$9$N$O(B<em>$BHs>o(B</em>$B$K8zN($,0-$$$H$$$&$3$H$K(B + $BCm0U$7$F$/$@$5$$!#$=$N$h$&$J>l9g$O!"Be$o$j$K(B <a + href="mod_auth_dbm.html#authdbmuserfile">AuthDBMUserFile</a> + $B$r(B $B;H$C$F$/$@$5$$!#(B</p> + + <p>$B%;%-%e%j%F%#(B: AuthUserFile + $B$OI,$:%&%'%V%5!<%P$N%I%-%e%a%s%H%D%j!<$N30$K(B + $BJ]4I$7$F$/$@$5$$!#$=$l$,J]8n$7$F$$$k(B + $B%G%#%l%/%H%j$K$OCV$+$J$$$G$/$@$5$$!#(B + $B$=$&$G$J$$$H!"%/%i%$%"%s%H$,(B AuthUserFile + $B$r%@%&%s%m!<%I$G$-$F$7$^$$$^$9!#(B</p> + + <p><a href="core.html#authname">AuthName</a>, <a + href="core.html#authtype">AuthType</a>, <a + href="#authgroupfile">AuthGroupFile</a> + $B$b;2>H$7$F$/$@$5$$!#(B</p> + <hr /> + + <h2><a id="authauthoritative" + name="authauthoritative">AuthAuthoritative</a> + $B%G%#%l%/%F%#%V(B</h2> + <a href="directive-dict.html#Syntax" + rel="Help"><strong>$B9=J8(B:</strong></a> AuthAuthoritative + on|off<br /> + <a href="directive-dict.html#Default" + rel="Help"><strong>$B%G%U%)%k%H(B:</strong></a> + <code>AuthAuthoritative on</code><br /> + <a href="directive-dict.html#Context" + rel="Help"><strong>$B%3%s%F%-%9%H(B:</strong></a> + $B%G%#%l%/%H%j!"(B.htaccess<br /> + <a href="directive-dict.html#Override" + rel="Help"><strong>$B>e=q$-(B:</strong></a> AuthConfig<br /> + <a href="directive-dict.html#Status" + rel="Help"><strong>$B%9%F!<%?%9(B:</strong></a> Base<br /> + <a href="directive-dict.html#Module" + rel="Help"><strong>$B%b%8%e!<%k(B:</strong></a> mod_auth + + <p>AuthAuthoritative $B%G%#%l%/%F%#%V$rL@<(E*$K(B + <strong>'off'</strong> $B$K(B $B@_Dj$9$k$H!"(BuserID + $B$K9g$&(B <strong>userID $B$,L5$$(B</strong> $B$H$-$H!"(B + $B$=$l$K9g$&(B<strong>$B%k!<%k(B</strong>$B$,L5$$$H$-$K!"G'>Z$H8"8B$NIUM?$NN>J}$r(B + (<code>$B@_Dj(B</code> $B$d(B <code>modules.c</code> + $B$GDj5A$5$l$F$$$k(B $BJ}K!$G(B) + $B2<0L$N%b%8%e!<%k$KEO$9$3$H$r2DG=$K$7$^$9!#(B userID + $B$+%k!<%k$,;XDj$5$l$F$$$k$H$-$K$O!"DL>o$HF1$8%Q%9%o!<%I$H(B + $B%"%/%;%9$N%A%'%C%/$,9T$J$o$l!"@.8y$7$J$+$C$?>l9g$O(B + Authorization Required $B1~Ez$,JV$5$l$^$9!#(B</p> + + <p>$B$G$9$+$i!"(BuserID + $B$,J#?t$N%b%8%e!<%k$N%G!<%?%Y!<%9$K8=$l$?$j!"(B $B@5$7$$(B + <code>Require</code> + $B%G%#%l%/%F%#%V$,J#?t$N%b%8%e!<%k$KE,MQ$5$l$?$j(B + $B$9$k$H$-$O!":G=i$N%b%8%e!<%k$,;q3J$rD4::$7$^$9!#(BAuthAuthoritative + $B$N(B + $B@_Dj$K4X$o$i$:!"%"%/%;%9$ND4::$OJL$N%b%8%e!<%k$K$OEO$5$l$^$;$s!#(B</p> + + <p>$B$3$N%G%#%l%/%F%#%V$NIaDL$NMxMQJ}K!$O!"(B<a + href="mod_auth_db.html"><code>mod_auth_db.c</code></a>, <a + href="mod_auth_dbm.html"><code>mod_auth_dbm.c</code></a>, + <code>mod_auth_msql.c</code>, <a + href="mod_auth_anon.html"><code>mod_auth_anon.c</code></a> + $B$N$h$&$J%G!<%?%Y!<%9%b%8%e!<%k$H0l=o$K;H$&$b$N$G$9!#(B + $B$3$l$i$N%b%8%e!<%k$OBgItJ,$N%f!<%6$N;q3JD4::$r9T$J$&5!G=$rDs6!$7$^$9!#(B + $B$7$+$7!">.?t$N(B ($B4IM}<T4XO"$N(B) $B%"%/%;%9$ONI$/J]8n$5$l$F$$$k(B AuthUserFile + $B$KEO$5$l$^$9!#(B</p> + + <p><a href="directive-dict.html#Default" + rel="Help"><strong>$B%G%U%)%k%H(B:</strong></a> + $B%G%U%)%k%H$G$O@)8f$OEO$5$l$^$;$s!#(B $BCN$i$J$$(B userID + $B$d%k!<%k$N7k2L$O(B Authorization Require $B1~Ez$K$J$j$^$9!#(B + $B$G$9$+$i!"$3$N%G%#%l%/%F%#%V$r@_Dj$7$J$$$H%7%9%F%`$r0BA4$KJ]$D$3$H$,$G$-!"(B + NCSA $B$HF1$8F0:n$r$9$k$h$&$K$G$-$^$9!#(B</p> + + <dl> + <dt><b>$B%;%-%e%j%F%#(B:</b></dt> + + <dd>AuthUserFile + $B$OI,$:%&%'%V%5!<%P$N%I%-%e%a%s%H%D%j!<$N30$KJ]4I$7$F$/$@$5$$!#(B + $B$=$l$,J]8n$7$F$$$k(B + $B%G%#%l%/%H%j$K$OCV$+(B<em>$B$J$$(B</em>$B$G$/$@$5$$!#(B + $B$=$&$G$J$$$H!"%/%i%$%"%s%H$,(B AuthUserFile + $B$r%@%&%s%m!<%I$G$-$F$7$^$$$^$9!#(B</dd> + + <dd> + $B$^$?!"6u$N%f!<%6L>$d!"6u$N%Q%9%o!<%I$,5v2D$5$l$k$3$H$KCm0U$7$F$/$@$5$$(B + (Apache 1.3.20 $B$+$i(B)$B!#(B AuthUserFile $B$K%3%m%s(B + (':') $B$N$_$N9T$,$"$l$P!"(B + $BG'>Z;~$K%f!<%6L>$H%Q%9%o!<%I$,N>J}6&>JN,$5$l$?$H$-$K(B + '<code>Require valid-user</code>' + $B$O%"%/%;%9$r5v2D$7$^$9!#(B</dd> + </dl> + + <p><a href="core.html#authname">AuthName</a>, <a + href="core.html#authtype">AuthType</a>, <a + href="#authgroupfile">AuthGroupFile</a> + $B$b;2>H$7$F$/$@$5$$!#(B</p> + <hr /> + + <h3 align="CENTER">Apache HTTP Server Version 1.3</h3> + <a href="./"><img src="../images/index.gif" alt="Index" /></a> + <a href="../"><img src="../images/home.gif" alt="Home" /></a> + + </body> +</html> + diff --git a/usr.sbin/httpd/src/os/tpf/samples/linkhttp.dlm b/usr.sbin/httpd/src/os/tpf/samples/linkhttp.dlm new file mode 100644 index 00000000000..a4ee418c3e2 --- /dev/null +++ b/usr.sbin/httpd/src/os/tpf/samples/linkhttp.dlm @@ -0,0 +1,66 @@ +CHTA.dlm +DLMVERSION(<vv>) +CSTRTD(40) +CINET640 +buildmark.o +modules.o +ap/ap_base64.o +ap/ap_checkpass.o +ap/ap_cpystrn.o +ap/ap_ebcdic.o +ap/ap_execve.o +ap/ap_fnmatch.o +ap/ap_getpass.o +ap/ap_md5c.o +ap/ap_sha1.o +ap/ap_signal.o +ap/ap_slack.o +ap/ap_snprintf.o +ap/ap_strtol.o +main/alloc.o +main/buff.o +main/http_config.o +main/http_core.o +main/http_log.o +main/http_main.o +main/http_protocol.o +main/http_request.o +main/http_vhost.o +main/rfc1413.o +main/util.o +main/util_date.o +main/util_md5.o +main/util_script.o +main/util_uri.o +modules/standard/mod_access.o +modules/standard/mod_actions.o +modules/standard/mod_alias.o +modules/standard/mod_asis.o +modules/standard/mod_auth.o +modules/standard/mod_autoindex.o +modules/standard/mod_cgi.o +modules/standard/mod_dir.o +modules/standard/mod_env.o +modules/standard/mod_imap.o +modules/standard/mod_include.o +modules/standard/mod_log_config.o +modules/standard/mod_mime.o +modules/standard/mod_negotiation.o +modules/standard/mod_setenvif.o +modules/standard/mod_status.o +modules/standard/mod_userdir.o +os/tpf/cgetop.o +os/tpf/os.o +os/tpf/os-inline.o +regex/regcomp.o +regex/regerror.o +regex/regexec.o +regex/regfree.o +SYSLIB(<your-first-syslib-dsn>) +SYSLIB(<your-final-syslib-dsn>) +OBJLIB(<your-first-objlib-dsn>) +OBJLIB(<your-final-objlib-dsn>) +STUBS() +TARGET(<your-target-dsn-here>) +PRELINK(MAP) +LINK(AMODE=31 RMODE=ANY LIST XREF MAP) |