Hey I should have asked the questions more clearly.
Has anyone used mod_vhost, or mod_rewrite, some other way, or some combination, and implemented in production, dynamic virtual hosts of unique hundreds or more, sub domains. If so, which method did you use, and can you give us the configuration, or some idea, that you used. Is one method a significantly bigger system resource user? Thanks From: "Walter H." <walte...@mathemainzel.info<mailto:walte...@mathemainzel.info>> Organization: Home Reply-To: <users@httpd.apache.org<mailto:users@httpd.apache.org>> Date: Wednesday, March 12, 2014 11:31 AM To: <users@httpd.apache.org<mailto:users@httpd.apache.org>> Subject: Re: [users@httpd] dynamic virtual hosts Hi, On 12.03.2014 16:15, Rose, John B wrote: We have been experimenting with "mod vhost alias" and "mod rewrite" methods of dynamic virtual hosting They both work fine for … abc.persons.domain.com xyz.persons.domain.com Etc. We would also like to be able to do dynamic virtual hosting for a mixture of sub domains and domains … 111.subdomain1.domain.com subdomain1.domain.com 222.subdomain2.domain.com subdomain2.domain.com subdomain3.domain2.com subdomain4.domain2.com 1. Does any have preferences, pros, cons, what is best for scaling to hundreds of virtual hosts over years, etc between the alternative methods of dynamic virtual hosts configurations? 2. Has anyone used a method they think is best for dynamic virtual hosting for a mixture of domains and subdomains Is there a semantic reason for having this many subdomains? in present I can see many sites that make use of many subdomains for a not logic reason; for restrictive smart surfing this can be a very good feature - just block a subdomain, to prevent stupid javascripts or css files to be downloaded ;-) using scripts from foreign sites that are only used on client side is the worst, you can do; if these represent sites of individuals than it is a good idea to have each one his own subdomain for the complete individual's website; Greetings, Walter