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 ChrisPepper:
http://wiki.apache.org/httpd/Recipes/ExampleVhosts

The comment on the change is:
Clean up case & punctuation

------------------------------------------------------------------------------
  ## page was renamed from Recipies/ExampleVhosts
  = Example VirtualHost Configurations =
  
- The excerpts below shows some example !VirtualHost config's that can be used 
in Apache.
+ The excerpts below show some example name-based !VirtualHost configurations 
that can be used in Apache.
  
- For each port that you want to use to serve content, you will need to define 
these before configuring your !VirtualHosts.
+ For each TCP port that you want to use to serve content, you will need to 
define these before configuring your !VirtualHosts.
- You will need a Listen directive, and a !NameVirtualHost directive.
+ You will need both a Listen directive and a !NameVirtualHost directive.
  
  
  {{{
@@ -21, +21 @@

  
  }}}
  
- == Basic Setup, using Port 80, and Custom Log files ==
+ == Basic setup, using port 80, with custom log files ==
  
  {{{
  <VirtualHost *:80>
@@ -37, +37 @@

  </VirtualHost>
  }}}
  
- == Basic Setup, multiple virtual hosts, on Port 80 ==
+ == Basic setup, on port 80, with multiple virtual hosts ==
  
  {{{
  <VirtualHost *:80>
@@ -63, +63 @@

  
  }}}
  
- == Basic VirtualHost with Custom Log files, and authentication ==
+ == Basic VirtualHost with custom log files and authentication ==
  {{{
  <VirtualHost *:80>
    ServerName www.foo.com
@@ -79, +79 @@

  </VirtualHost>
  }}}
  
- == SSL enabled VirtualHost with Custom Log files ==
+ == SSL-enabled VirtualHost with custom log files ==
  {{{
  <VirtualHost _default_:443>
    # Only one virtual host allowed on this port, because name-based
-   # v-hosting doesn't work with SSL
+   # virtual hosting doesn't work with SSL
    ServerName www.foo.com
    DocumentRoot /var/www/www.foo.com/htdocs
  

Reply via email to