httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sl...@apache.org
Subject cvs commit: httpd-docs-1.3/htdocs/manual bind.html.en
Date Sat, 02 Jun 2001 20:34:24 GMT
slive       01/06/02 13:34:24

  Modified:    htdocs/manual bind.html.en
  Log:
  Touchups to bind.html.
  
  Submitted by:	Jason Lingohr <jason@lucid.net.au>
  Reviewed by:	Joshua Slive
  
  Revision  Changes    Path
  1.16      +28 -23    httpd-docs-1.3/htdocs/manual/bind.html.en
  
  Index: bind.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/bind.html.en,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -d -b -u -r1.15 -r1.16
  --- bind.html.en	2000/11/22 02:58:18	1.15
  +++ bind.html.en	2001/06/02 20:34:24	1.16
  @@ -57,10 +57,10 @@
    REL="Help"
   ><STRONG>Status:</STRONG></A> Core<P>
   
  -Makes the server listen to just the specified address. If the argument
  -is *, the server listens to all addresses. The port listened to
  -is set with the <TT>Port</TT> directive. Only one BindAddress
  -should be used.
  +Makes the server bind to just the specified address. If the argument is
  +* (an asterisk), the server binds to all interfaces currently marked
  +as up on the server. The port bound to is set with the <TT>Port</TT>
  +directive. Only one BindAddress should be used.
   
   <H3><A NAME="listen">Listen</A></H3>
   <A
  @@ -81,14 +81,14 @@
   ><STRONG>Status:</STRONG></A> Core<P>
   
   <TT>Listen</TT> can be used instead of <TT>BindAddress</TT> and
  -<TT>Port</TT>. It tells the server to accept incoming requests on the
  -specified port or address-and-port combination. If the first format is
  -used, with a port number only, the server listens to the given port on
  -all interfaces, instead of the port given by the <TT>Port</TT>
  -directive. If an IP address is given as well as a port, the server
  -will listen on the given port and interface.  <P> Multiple Listen
  -directives may be used to specify a number of addresses and ports to
  -listen to. The server will respond to requests from any of the listed
  +<TT>Port</TT>. It tells the server to accept incoming requests (to listen)
  +on the specified port or address-and-port combination. If the first
  +format is used, with a port number only, the server listens on the given
  +port on all interfaces marked as up, instead of the port given by the
  +<TT>Port</TT> directive. If an IP address is given as well as a port,
  +the server will listen on the given port and interface.  <P> Multiple
  +Listen directives may be used to specify a number of addresses and ports
  +to listen to. The server will respond to requests from any of the listed
   addresses and ports.<P>
   
   For example, to make the server accept connections on both port
  @@ -107,17 +107,22 @@
   
   <H2>How this works with Virtual Hosts</H2>
   
  -BindAddress and Listen do not implement Virtual Hosts. They tell the
  -main server what addresses and ports to listen to.  If no
  -&lt;VirtualHost&gt; directives are used, the server will behave the
  -same for all accepted requests. However, &lt;VirtualHost&gt; can be
  -used to specify a different behavior for one or more of the addresses
  -and ports. To implement a VirtualHost, the server must first be told
  -to listen to the address and port to be used. Then a
  -&lt;VirtualHost&gt; section should be created for a specified address
  -and port to set the behavior of this virtual host. Note that if the
  -&lt;VirtualHost&gt; is set for an address and port that the server is
  -not listening to, it cannot be accessed.
  +<TT>BindAddress</TT> and <TT>Listen</TT> do not implement Virtual
  +Hosts. They tell the main Apache daemon process what addresses and ports
  +to bind and listen on.  If no &lt;VirtualHost&gt; directives are used,
  +the server will behave the same for all accepted requests. However,
  +&lt;VirtualHost&gt; can be used to specify a different behavior for
  +one or more of the addresses and ports. To implement a VirtualHost,
  +the server must:
  +
  +<UL>
  +<LI>Be told to <TT>Listen</TT> to the desired address and port
  +<LI>Have a &lt;VirtualHost&gt; section created for the
  +  specified address and port to set the behavior of this virtual host
  +</UL>
  +
  +Note that if the &lt;VirtualHost&gt; is set for an address and port that
  +the server is not listening to, it cannot be accessed.
   
   <H2>See also</H2>
   
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: apache-docs-unsubscribe@apache.org
For additional commands, e-mail: apache-docs-help@apache.org


Mime
View raw message