<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 420990 -->
+<!-- English Revision: 420990:926536 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<?xml version="1.0" encoding="EUC-KR" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>
-<!-- English Revision: 151408:420990 (outdated) -->
+<!-- English Revision: 151408:926536 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<variants>
<variant>en</variant>
<variant>fr</variant>
- <variant>ja</variant>
+ <variant outdated="yes">ja</variant>
<variant outdated="yes">ko</variant>
</variants>
</metafile>
bytes per request (*)</li>
<li>The current percentage CPU used by each worker and in
- total by Apache (*)</li>
+ total by all workers combined (*)</li>
<li>The current hosts and requests being processed (*)</li>
</ul>
<p>A machine-readable version of the status file is available by
accessing the page
<code>http://your.server.name/server-status?auto</code>. This
- is useful when automatically run, see the Perl program in the
- <code>/support</code> directory of Apache,
- <code>log_server_status</code>.</p>
+ is useful when automatically run, see the Perl program
+ <code>log_server_status</code>, which you will find in the
+ <code>/support</code> directory of your Apache HTTP Server installation.</p>
<div class="note">
<strong>It should be noted that if <code class="module"><a href="../mod/mod_status.html">mod_status</a></code> is
bytes per request (*)</li>
<li>The current percentage CPU used by each worker and in
- total by Apache (*)</li>
+ total by all workers combined (*)</li>
<li>The current hosts and requests being processed (*)</li>
</ul>
<p>A machine-readable version of the status file is available by
accessing the page
<code>http://your.server.name/server-status?auto</code>. This
- is useful when automatically run, see the Perl program in the
- <code>/support</code> directory of Apache,
- <code>log_server_status</code>.</p>
+ is useful when automatically run, see the Perl program
+ <code>log_server_status</code>, which you will find in the
+ <code>/support</code> directory of your Apache HTTP Server installation.</p>
<note>
<strong>It should be noted that if <module>mod_status</module> is
<tr><th><a href="module-dict.html#Status">Status:</a></th><td>Experimental</td></tr>
<tr><th><a href="module-dict.html#ModuleIdentifier">Module Identifier:</a></th><td>substitute_module</td></tr>
<tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_substitute.c</td></tr>
-<tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache 2.2.7 and later</td></tr></table>
+<tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache HTTP Server 2.2.7 and later</td></tr></table>
<h3>Summary</h3>
<p><code class="module"><a href="../mod/mod_substitute.html">mod_substitute</a></code> provides a mechanism to perform
<status>Experimental</status>
<sourcefile>mod_substitute.c</sourcefile>
<identifier>substitute_module</identifier>
-<compatibility>Available in Apache 2.2.7 and later</compatibility>
+<compatibility>Available in Apache HTTP Server 2.2.7 and later</compatibility>
<summary>
<p><module>mod_substitute</module> provides a mechanism to perform
redirect to <code>http://www.example.com/bob/one/two.html</code>.</p>
<p>If you add a redirect, it must be the last alternative in the list.
- Apache cannot determine if the redirect succeeded or not, so if you have
+ Apache httpd cannot determine if the redirect succeeded or not, so if you have
the redirect earlier in the list, that will always be the alternative
that is used.</p>
<h3>See also</h3>
<ul>
<li>
- <a href="../howto/public_html.html">public_html tutorial</a>
+ <a href="../howto/public_html.html">Per-user web directories tutorial</a>
</li>
</ul>
</div>
redirect to <code>http://www.example.com/bob/one/two.html</code>.</p>
<p>If you add a redirect, it must be the last alternative in the list.
- Apache cannot determine if the redirect succeeded or not, so if you have
+ Apache httpd cannot determine if the redirect succeeded or not, so if you have
the redirect earlier in the list, that will always be the alternative
that is used.</p>
</usage>
<seealso>
- <a href="../howto/public_html.html">public_html tutorial</a>
+ <a href="../howto/public_html.html">Per-user web directories tutorial</a>
</seealso>
</directivesynopsis>
</table>
<p>The <code class="directive">VirtualDocumentRoot</code> directive allows you to
- determine where Apache will find your documents based on the
+ determine where Apache HTTP Server will find your documents based on the
value of the server name. The result of expanding
<em>interpolated-directory</em> is used as the root of the
document tree in a similar manner to the <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> directive's argument.
</table>
<p>The <code class="directive">VirtualScriptAlias</code> directive allows you to
- determine where Apache will find CGI scripts in a similar
+ determine where Apache httpd will find CGI scripts in a similar
manner to <code class="directive"><a href="#virtualdocumentroot">VirtualDocumentRoot</a></code> does for other documents. It matches
requests for URIs starting <code>/cgi-bin/</code>, much like <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code>
<code>/cgi-bin/</code> would.</p>
<usage>
<p>The <directive>VirtualDocumentRoot</directive> directive allows you to
- determine where Apache will find your documents based on the
+ determine where Apache HTTP Server will find your documents based on the
value of the server name. The result of expanding
<em>interpolated-directory</em> is used as the root of the
document tree in a similar manner to the <directive
<usage>
<p>The <directive>VirtualScriptAlias</directive> directive allows you to
- determine where Apache will find CGI scripts in a similar
+ determine where Apache httpd will find CGI scripts in a similar
manner to <directive module="mod_vhost_alias"
>VirtualDocumentRoot</directive> does for other documents. It matches
requests for URIs starting <code>/cgi-bin/</code>, much like <directive