Listen Directives

Listen Directives

Post by Lisa Dunla » Sun, 10 Sep 2000 04:19:45



    Why would anyone use the following Listen directives for an Apache
configuration file when there is only one IP address (138.23.135.145) for a
server?

Listen 3000
Listen 12.34.56.78:80
(Configuration file has Port directive set at 80; BindAddress directive is
*)

 
 
 

Listen Directives

Post by Richard Homolk » Sun, 10 Sep 2000 06:13:19



>     Why would anyone use the following Listen directives for an Apache
> configuration file when there is only one IP address (138.23.135.145) for a
> server?

> Listen 3000
> Listen 12.34.56.78:80

Those are just examples for what you can do.  If you had more than one
IP address for your server (multiple NIC cards, IP aliases on a card)
then it owuld make sense.  If you don't need it, you don't need it.

--
---------------------------------------------------------------------
Richard Homolka        Zedo inc.                       (415) 348-1975


 
 
 

1. (newbie. ) listen directive question?

For the Listen directive....

The Apache online manual says:
Note that you may still require a Port directive so that URLs that
Apache generates that point to your server still work.

but what does this mean .. i dont get it.

why would the port directive be required to be mentioned, when the
listen directive takes care of both the ip addr. and the port?

2. ftp-ing to a printer

3. Apache : LISTEN directive and SERVER_PORT environment Variable, HELP

4. IE: cannot read byteserved pdf file (Apache2 only)

5. Apache Listen directive

6. DOS virus detection on UNIX

7. Unable to have multiple Listen directives with Apache 2.0.16

8. Cannot run netcfg

9. Apache listen directive make server load high.

10. Trouble with Listen directive and Apache 1.1.1

11. Apache and Listen Directive not working

12. Disable/undo directives in deeper config scopes, here: Action directive

13. apache listen to port 80, another standalone apache+modssl listen port 443, not working..?!