From 3cee2cd1c0992519b27b5947c75cbf9935e6cefe Mon Sep 17 00:00:00 2001 From: =?utf8?q?Andr=C3=A9=20Malo?= Date: Thu, 6 Feb 2014 16:45:29 +0000 Subject: [PATCH] add example containers git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1565335 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/bind.xml | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/docs/manual/bind.xml b/docs/manual/bind.xml index 15428a91a8..888ef9387e 100644 --- a/docs/manual/bind.xml +++ b/docs/manual/bind.xml @@ -71,32 +71,38 @@

For example, to make the server accept connections on both port 80 and port 8000, on all interfaces, use:

+ Listen 80 Listen 8000 +

To make the server accept connections on port 80 for one interface, and port 8000 on another, use

+ Listen 192.0.2.1:80 Listen 192.0.2.5:8000 +

IPv6 addresses must be enclosed in square brackets, as in the following example:

+ Listen [2001:db8::a00:20ff:fea7:ccea]:80 +

Overlapping Listen directives will result in a fatal error which will prevent the server from starting up.

- (48)Address already in use: make_sock: could not bind to address [::]:80 + (48)Address already in use: make_sock: could not bind to address [::]:80

See Listen directives, as in the following examples:

+ Listen 0.0.0.0:80 Listen 192.0.2.1:80 +

If your platform supports it and you want httpd to handle IPv4 and IPv6 connections on separate sockets (i.e., to disable IPv4-mapped @@ -167,9 +175,11 @@ Listen 192.0.2.1:80

You only need to set the protocol if you are running on non-standard ports. For example, running an https site on port 8443:

+ Listen 192.170.2.1:8443 https +
-- 2.40.0