Received: by taz.hyperreal.com (8.6.12/8.6.5) id DAA09105; Tue, 23 Jan 1996 03:51:09 -0800 Received: from cass41 by taz.hyperreal.com (8.6.12/8.6.5) with SMTP id DAA09084; Tue, 23 Jan 1996 03:50:42 -0800 Received: from mamba.ast.cam.ac.uk by cass41 with smtp (Smail3.1.29.1 #9) id m0tehEk-000CM6C; Tue, 23 Jan 96 11:50 GMT Received: by mamba.ast.cam.ac.uk (Smail3.1.29.1 #9) id m0tehEj-0000kFC; Tue, 23 Jan 96 11:50 GMT Message-Id: Date: Tue, 23 Jan 96 11:50 GMT From: drtr@ast.cam.ac.uk (David Robinson) To: new-httpd@hyperreal.com Subject: Re: Proxy module available... use at own risk. Content-Length: 3196 Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com Alexei wrote: >> from the remote server, I also try to avoid breaking on >> A-Header: xxx >> A-Header: yyy > >I don't break. I merge. Combine them to A-Header: xxx, yyy - perfectly >legal. Yes, it's legal; I just wish it didn't cause any problems (as it does with the netscape cookies, sigh). > > > > > > > > >which would enable restrictions for just access to www.apache.org. And so > > >forth. Common sense probably works here. > > > > Hmm, I chose to have all these 'filenames' prefixed with the module name, > > i.e. > > > > ... > > this wastes less of the namespace, and suggests this as a general feature > > (for 1.1) for mapping 'modules' into the URL space. e.g. you write a > > stats module which returns statistics about the server, you would protect > > it with > > >However, stats is not something that can really be returned by the >server. Yes it is! The server could return a page like Apache server statistics Number of active children: 10 etc... >A file is. A proxy URL is. What I'm getting at is that your >"general feature" is as much of a hack as mine is, but mine is more >intuitive. should be replaced with something else, because, >as it says, it's not protecting a directory in this case. At any rate, I >think people would rather use http: then proxy:http:, which doesn't make >a lot of sense. Well, sure it is a hack, but it seemed the simplest 'hack' for 1.0. Ideally there would be another tag instead of 'Directory' for protecting these objects (proxy requests etc.) But as yet, there isn't. One advantage of putting the module name in there is so that protects the _entire_ proxy server functionality. Otherwise, to restrict access to the proxy server one would have to list all the protocols it supported, i.e. lots of stuff lots of stuff etc... > > >Pass /apache/ http://www.apache.org/ > > > > > >Which does the obvious. > > > > I think it is neater (and more general) to have > > Alias /apache/ proxy:http://www.apache.org/ > > It may be "neater", but it makes a heck of lot less sense to the user. It > As much as you may think it looks like a "general solution", it screams to > me "hack! hack! hack! hack! hack!", since proxy: is and will never be a > filename for Alias to point at. Pass at least makes sense, since both > parts are URLs (or partial URLs), and can be happy that way. Well, what syntax would you suggest for including objects in the URL space of the server which don't map to files? Yes, one could have a new ad hoc directive for each object, i.e. Pass /apache/ http://www.apache.org/ ServerStats /stats # URL to access server statistics RemoteConfigure /config # URL to reconfigure server but wouldn't some combined syntax be better? Perhaps Install