On Mon, Dec 17, 2001 at 11:25:09AM -0700, Bryan Field-Elliot wrote: > solution #2 - I'm afraid I don't quite understand what you're saying. > I'm already using NameVirtualHost. The rest of what you describe isn't > quite making sense to me as far as what I actually have to do.
Sorry, my mistake. I thought of mass virtual hosting (http://httpd.apache.org/docs/vhosts/mass.html) but spoke of simple name based virtual host. The point of using mass virtual hosting is condencing your httpd.conf just to: UseCanonicalName Off LogFormat "%V %h %l %u %t \"%r\" %s %b" vcommon CustomLog logs/access_log vcommon # include the server name in the filenames used to satisfy requests VirtualDocumentRoot /www/hosts/%0/docs VirtualScriptAlias /www/hosts/%0/cgi-bin And thus all your _non-SSL_ hosts are now configured and to add a new one requires just the creation of the path. Alas, you would still have to create all SSL vhosts by hand... Another way would be a creation of a simple perl script that upon the request for apache's start or restart would read a configuration file that just listed the hostname (and possible responsible person's address), and from that created all needed configuration for those virtual hosts and joined that to apache's global configuration. Regards, Luciano Rocha -- Luciano Rocha, [EMAIL PROTECTED] The trouble with computers is that they do what you tell them, not what you want. -- D. Cohen ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
