You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ma...@apache.org on 2001/10/14 17:35:05 UTC
cvs commit: httpd-2.0/docs/manual/vhosts details.html ip-based.html
martin 01/10/14 08:35:05
Modified: docs/manual suexec.html
docs/manual/misc security_tips.html
docs/manual/mod mod_info.html
docs/manual/vhosts details.html ip-based.html
Log:
Fix broken links
Revision Changes Path
1.26 +3 -3 httpd-2.0/docs/manual/suexec.html
Index: suexec.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/suexec.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- suexec.html 2001/09/22 18:53:20 1.25
+++ suexec.html 2001/10/14 15:35:04 1.26
@@ -390,7 +390,7 @@
<dt><code>--suexec-caller=<em>UID</em></code></dt>
- <dd>The <a href="mod/core.html#user">username</a> under which
+ <dd>The <a href="mod/mpm_common.html#user">username</a> under which
Apache normally runs. This is the only user allowed to
execute this program.</dd>
@@ -523,8 +523,8 @@
<p align="LEFT"><strong>Virtual Hosts:</strong><br />
One way to use the suEXEC wrapper is through the <a
- href="mod/core.html#user">User</a> and <a
- href="mod/core.html#group">Group</a> directives in <a
+ href="mod/mpm_common.html#user">User</a> and <a
+ href="mod/mpm_common.html#group">Group</a> directives in <a
href="mod/core.html#virtualhost">VirtualHost</a> definitions.
By setting these directives to values different from the main
server user ID, all requests for CGI resources will be executed
1.26 +1 -1 httpd-2.0/docs/manual/misc/security_tips.html
Index: security_tips.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/misc/security_tips.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- security_tips.html 2001/10/05 21:26:00 1.25
+++ security_tips.html 2001/10/14 15:35:04 1.26
@@ -44,7 +44,7 @@
<p>In typical operation, Apache is started by the root user,
and it switches to the user defined by the <a
- href="../mod/core.html#user"><strong>User</strong></a>
+ href="../mod/mpm_common.html#user"><strong>User</strong></a>
directive to serve hits. As is the case with any command that
root executes, you must take care that it is protected from
modification by non-root users. Not only must the files
1.13 +1 -1 httpd-2.0/docs/manual/mod/mod_info.html
Index: mod_info.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_info.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- mod_info.html 2001/09/22 19:36:01 1.12
+++ mod_info.html 2001/10/14 15:35:04 1.13
@@ -60,7 +60,7 @@
configuration if the files have been changed since the server
was last reloaded. Also, the configuration files must be
readable by the user as which the server is running (see the
- <a href="core.html#user"><samp>User</samp></a> directive), or
+ <a href="mpm_common.html#user"><samp>User</samp></a> directive), or
else the directive settings will not be listed.</strong>
<p><strong>It should also be noted that if
1.13 +1 -1 httpd-2.0/docs/manual/vhosts/details.html
Index: details.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/vhosts/details.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- details.html 2001/09/22 19:39:26 1.12
+++ details.html 2001/10/14 15:35:04 1.13
@@ -58,7 +58,7 @@
legacy compatibility with NCSA configuration files. One
function is to determine the default network port Apache will
bind to. This default is overridden by the existence of any <a
- href="../mod/core.html#listen"><code>Listen</code></a>
+ href="../mod/mpm_common.html#listen"><code>Listen</code></a>
directives. The second function is to specify the port number
which is used in absolute URIs during redirects.</p>
1.9 +7 -7 httpd-2.0/docs/manual/vhosts/ip-based.html
Index: ip-based.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/vhosts/ip-based.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- ip-based.html 2001/09/22 19:39:26 1.8
+++ ip-based.html 2001/10/14 15:35:04 1.9
@@ -41,9 +41,9 @@
does not want anyone at company2 to be able to read their
data except via the web. In this case you would need two
daemons, each running with different <a
- href="../mod/core.html#user">User</a>, <a
- href="../mod/core.html#group">Group</a>, <a
- href="../mod/core.html#listen">Listen</a>, and <a
+ href="../mod/mpm_common.html#user">User</a>, <a
+ href="../mod/mpm_common.html#group">Group</a>, <a
+ href="../mod/mpm_common.html#listen">Listen</a>, and <a
href="../mod/core.html#serverroot">ServerRoot</a>
settings.</li>
@@ -51,7 +51,7 @@
href="../misc/descriptors.html">file descriptor
requirements</a> of listening to every IP alias on the
machine. It's only possible to <a
- href="../mod/core.html#listen">Listen</a> to the "wildcard"
+ href="../mod/mpm_common.html#listen">Listen</a> to the "wildcard"
address, or to specific addresses. So if you have a need to
listen to a specific address for whatever reason, then you
will need to listen to all specific addresses. (Although one
@@ -72,7 +72,7 @@
<h2>Setting up multiple daemons</h2>
Create a separate httpd installation for each virtual host. For
each installation, use the <a
- href="../mod/core.html#listen">Listen</a> directive in the
+ href="../mod/mpm_common.html#listen">Listen</a> directive in the
configuration file to select which IP address (or virtual host)
that daemon services. e.g.
<pre>
@@ -122,8 +122,8 @@
href="../mod/directive-dict.html#Context">Context</a> using the
<a href="../mod/directives.html">directive index</a>.</p>
- <p><a href="../mod/core.html#user">User</a> and <a
- href="../mod/core.html#group">Group</a> may be used inside a
+ <p><a href="../mod/mpm_common.html#user">User</a> and <a
+ href="../mod/mpm_common.html#group">Group</a> may be used inside a
VirtualHost directive if the <a href="../suexec.html">suEXEC
wrapper</a> is used.</p>