You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by tr...@apache.org on 2002/02/19 15:29:52 UTC
cvs commit: httpd-2.0/docs/manual/mod core.html mod_access.html mod_access.xml mpm_common.html
trawick 02/02/19 06:29:51
Modified: docs/manual bind.html
docs/manual/mod core.html mod_access.html mod_access.xml
mpm_common.html
Log:
Describe IPv6 syntax for Listen, Allow from, and <VirtualHost >.
Revision Changes Path
1.19 +36 -0 httpd-2.0/docs/manual/bind.html
Index: bind.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/bind.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- bind.html 19 Oct 2001 06:05:39 -0000 1.18
+++ bind.html 19 Feb 2002 14:29:51 -0000 1.19
@@ -47,6 +47,42 @@
Listen 192.170.2.1:80
Listen 192.170.2.5:8000
</pre>
+ IPv6 addresses must be surrounded in square brackets, as in the
+ following example:
+<pre>
+ Listen [fe80::a00:20ff:fea7:ccea]:80
+</pre>
+
+ <h2>Special IPv6 considerations</h2>
+
+ When APR supports IPv6, Apache will create IPv6-capable listening
+ sockets by default (i.e., when no IP address is specified on the
+ Listen directive). In other words, when APR supports IPv6,
+<pre>
+ Listen 80
+</pre>
+ is equivalent to
+<pre>
+ Listen [::]:80
+</pre>
+ When APR does not support IPv6,
+<pre>
+ Listen 80
+</pre>
+ is equivalent to
+<pre>
+ Listen 0.0.0.0:80
+</pre>
+ On some platforms, such as NetBSD, binding to the IPv6 wildcard address
+ ("::") does not allow Apache to accept connections on IPv4 interfaces.
+ In this situation, multiple Listen directives are required, as shown
+ below:
+<pre>
+ Listen 0.0.0.0:80
+ Listen [::]:80
+</pre>
+ Apache does not currently detect this, so the Listen statements must
+ be edited manually by the administrator.
<h2>How this works with Virtual Hosts</h2>
1.214 +17 -2 httpd-2.0/docs/manual/mod/core.html
Index: core.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/core.html,v
retrieving revision 1.213
retrieving revision 1.214
diff -u -r1.213 -r1.214
--- core.html 12 Feb 2002 20:17:57 -0000 1.213
+++ core.html 19 Feb 2002 14:29:51 -0000 1.214
@@ -2874,14 +2874,29 @@
TransferLog logs/host.foo.com-access_log<br />
</VirtualHost></code>
</blockquote>
- Each VirtualHost must correspond to a different IP address,
+
+ <p>IPv6 addresses must be specified in square brackets because
+ the optional port number could not be determined otherwise. An
+ IPv6 example is shown below:</p>
+
+ <blockquote>
+ <code><VirtualHost [fe80::a00:20ff:fea7:ccea]><br />
+ ServerAdmin webmaster@host.foo.com<br />
+ DocumentRoot /www/docs/host.foo.com<br />
+ ServerName host.foo.com<br />
+ ErrorLog logs/host.foo.com-error_log<br />
+ TransferLog logs/host.foo.com-access_log<br />
+ </VirtualHost></code>
+ </blockquote>
+
+ <p>Each VirtualHost must correspond to a different IP address,
different port number or a different host name for the server,
in the former case the server machine must be configured to
accept IP packets for multiple addresses. (If the machine does
not have multiple network interfaces, then this can be
accomplished with the <code>ifconfig alias</code> command (if
your OS supports it), or with kernel patches like <a
- href="../misc/vif-info.html">VIF</a> (for SunOS(TM) 4.1.x)).
+ href="../misc/vif-info.html">VIF</a> (for SunOS(TM) 4.1.x)).</p>
<p>The special name <code>_default_</code> can be specified in
which case this virtual host will match any IP address that is
1.29 +8 -0 httpd-2.0/docs/manual/mod/mod_access.html
Index: mod_access.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_access.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- mod_access.html 31 Dec 2001 02:29:12 -0000 1.28
+++ mod_access.html 19 Feb 2002 14:29:51 -0000 1.29
@@ -145,6 +145,14 @@
<p>Note that the last three examples above match exactly the
same set of hosts.</p>
+ <p>IPv6 addresses and IPv6 subnets can be specified as shown
+ below:</p>
+
+ <pre>
+ Allow from fe80::a00:20ff:fea7:ccea
+ Allow from fe80::a00:20ff:fea7:ccea/10
+ </pre>
+
<p>The third format of the arguments to the <code>Allow</code>
directive allows access to the server to be controlled based on
the existence of an <a href="../env.html">environment
1.2 +8 -0 httpd-2.0/docs/manual/mod/mod_access.xml
Index: mod_access.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_access.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- mod_access.xml 15 Feb 2002 18:02:19 -0000 1.1
+++ mod_access.xml 19 Feb 2002 14:29:51 -0000 1.2
@@ -118,6 +118,14 @@
<p>Note that the last three examples above match exactly the
same set of hosts.</p>
+ <p>IPv6 addresses and IPv6 subnets can be specified as shown
+ below:</p>
+
+ <example>
+ Allow from fe80::a00:20ff:fea7:ccea
+ Allow from fe80::a00:20ff:fea7:ccea/10
+ </example>
+
<p>The third format of the arguments to the
<directive>Allow</directive> directive allows access to the server
to be controlled based on the existence of an <a
1.19 +5 -0 httpd-2.0/docs/manual/mod/mpm_common.html
Index: mpm_common.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mpm_common.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- mpm_common.html 30 Dec 2001 19:30:57 -0000 1.18
+++ mpm_common.html 19 Feb 2002 14:29:51 -0000 1.19
@@ -217,6 +217,11 @@
Listen 192.170.2.1:80
Listen 192.170.2.5:8000
</pre>
+ IPv6 addresses must be surrounded in square brackets, as in the
+ following example:
+<pre>
+ Listen [fe80::a00:20ff:fea7:ccea]:80
+</pre>
<p><strong>See Also:</strong> <a href="../dns-caveats.html">DNS
Issues</a><br />