Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Httpd Wiki" for change 
notification.

The following page has been changed by slive:
http://wiki.apache.org/httpd/ScratchPad/CommonMisconfigurations

The comment on the change is:
No line-end comments in apache + spelling

------------------------------------------------------------------------------
  ==== 4. Using the same Listen and/or NameVirtualHost multiple times. ====
  Example:
  {{{# Can happen when using multiple config files.
- Listen 80 # In one config file
+ # In one config file:
+ Listen 80 
- Listen 80 # In another config file
+ # In another config file:
+ Listen 80 
  
- # Like above, can happen when using multipe config files.
+ # Like above, can happen when using multiple config files.
- NameVirtualHost *:80 # In one config file
- NameVirtualHost *:80 # In another config file.
+ # In one config file:
+ NameVirtualHost *:80
+ # In another config file: 
+ NameVirtualHost *:80 
  }}}
  
  In the case of multiple Listen directives, Apache will bind to port 80 the 
first time and then again try to bind to port 80 the second time yielding a 
nice "Could not bind to port" error on start up. This seems to happen with 
newbies and Debian based distros, where Debian based distros have Listen 80 
defined in ports.conf. Newbies don't realize this and create another Listen 80 
line in apache2.conf.[[BR]][[BR]]
  
  Multiple !NameVirtualHost lines will yield a "!NameVirtualHost *:80 has no 
!VirtualHosts" warning. Apache will ignore the second directive and use the 
first defined !NameVirtualHost line, though. This seems to happen when one is 
using multiple virtual host configuration files and doesn't understand that you 
only need to define a particular !NameVirtualHost line once.[[BR]][[BR]]
  
- ==== 5. Mutliple SSL name based virtual hosts on the same interface. ====
+ ==== 5. Multiple SSL name based virtual hosts on the same interface. ====
  Example:
  {{{NameVirtualHost *:443
  

Reply via email to