Project

General

Profile

History

Docs ยป

Mod evhost » History » Revision 19

Revision 18 (nitrox, 2008-10-18 21:51) → Revision 19/23 (heavyhttpd, 2009-01-11 03:56) 


 h1. Enhanced Virtual-Hosting 

 *Module: mod_evhost* 

 {{>toc}} 

 h2. Description 

 mod_evhost builds the document-root based on a pattern which contains 
 wildcards. Those wildcards can represent parts of the submitted hostname 
 
 <pre> 
   %% => % sign 
   %0 => domain name + tld 
   %1 => tld 
   %2 => domain name without tld 
   %3 => subdomain 1 name 
   %4 => subdomain 2 name 
 </pre> 

   evhost.path-pattern = "/home/www/servers/%3/pages/" 

 Note that % patterns in evhost.path-pattern have the special meanings listed above.    They do *not* have the standard meanings for % patterns defined by the lighttpd configuration file syntax. 

 


 h2. Options 

 evhost.path-pattern  
   pattern with wildcards to be replace to build a documentroot 


 h2. Samples 


 *User vhosts* 


 <pre> 
   $HTTP["host"] =~ "users\.example\.org" { 
       evhost.path-pattern = "/home/%4/public_html/" 
   } 
 </pre> 

 http://johndoe.users.example.org/ => /home/johndoe/public_html/ 

 h2. General Example 

 <pre> 
   server.document-root = "/home/user/sites/default/site" "/home/user/sites/" 
   evhost.path-pattern    = "/home/user/sites/%0/site/" 
 </pre> 

 If example.org is requested, and /home/user/sites/example.org/site/ is found, that path becomes the docroot. 

 If example.net is requested but no directory named /home/user/sites/example.net/site/ exists, is not found in ''/home/user/sites/ then the docroot remains /home/user/sites/default/site as /home/user/sites/ 

 h2. A Bad Example 

 <pre> 
   This is actually a bad example. server.document-root = "/home/user/sites/" 
   evhost.path-pattern    = "/home/user/sites/%0/site/" 
 </pre> 

 server.document-root should never point to the directory with your evhost subdirs. 
 Here's why: Assume 

 Let us assume we got foo.example.com and bar.example.com both point pointing to the server. 
 Assume that 

 for foo.example.com we have /home/user/sites/foo.example.com/site exists, but /home/user/sites/bar.example.com/site does not. for bar no directory exists. 

 If For foo.example.com is configured via mod_auth: we configure auth via: 

 <pre> 
   $HTTP["host"] == "foo.example.com" { 
     auth.require = ( "/" => ... 
     )  
   } 
 </pre> 

 We could If we now access http://bar.example.com/foo.example.com/site/ we bypass the configured auth by accessing http://bar.example.com/foo.example.com/site/ in the vhost block. 

 A better example would be 

 <pre> 
   server.document-root = "/home/user/sites/default/site" 
   evhost.path-pattern    = "/home/user/sites/%0/site/" 
 </pre>