Received: by taz.hyperreal.com (8.6.12/8.6.5) id SAA04534; Sat, 1 Jun 1996 18:02:19 -0700 Received: from fully.organic.com by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id SAA04522; Sat, 1 Jun 1996 18:02:16 -0700 Received: (from brian@localhost) by fully.organic.com (8.6.12/8.6.12) id BAA00294; Sun, 2 Jun 1996 01:06:04 GMT Date: Sat, 1 Jun 1996 18:06:02 -0700 (PDT) From: Brian Behlendorf To: new-httpd@hyperreal.com cc: new-httpd@hyperreal.com Subject: Re: No HOST header solutions? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com On Sat, 1 Jun 1996, Alexei Kosut wrote: > Some of it has to go in the core, yeah. The reson for that is so that > you can identify the correct virtual host, something you can't do from > a module or, especially, from a CGI script. This is the main > disadvantage with the approach in host.html using Alias, and was what > Rob Hartill was complaining about. > > Using the Alias approach, with non-Host-sending browsers, the requests > end up being in the main server's config setup, not the virtual > server's. So if you have seperate log files, they end up in the wrong > place. Similarly with redirects and error messages and all that other > fun stuff that can't be set per-directory. There are other things such an infrastructure should probably support for people to really trust it - setting the DOCUMENT_ROOT variable to the vhost's, modifying paths relative to docroot in parsed HTML files and imap files, etc. It just feels like the slippery slope, that if we make the implicit promise that this will "work", there's a lot of extra cruft that will end up in the server because people rely on this. It's not hard to write a perl tool which will pluck out requests for /vhost/* in the original server's logfiles, strip off the "/vhost" from the object name in the request, and merge it into the vhost's logfiles. it's also not hard to write a perl tool to take directives and map them into a or section, too. I'm just in a really big KISS streak recently, and while I don't care as much about cruft being added to modules, cruft in the core *must* be highly justified. I can definitely see how doing so here alleviates certain inconveniences, but I'd rather see if there's out-of-band solutions. Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- brian@organic.com | We're hiring! http://www.organic.com/Home/Info/Jobs/