On Wed, Nov 01, 2000 at 10:47:02PM +0200, Moshe Zadka wrote:
> On Wed, 1 Nov 2000, Sean R. Lynch wrote:
> > I don't know about the other issues, but perhaps web applications could all
> > be installed in a standard subdirectory under a "standard" htdocs location,
> > i.e. packages, with the user warned not to put their own stuff there. Then
> > if the user has their htdocs directory somewhere else, they could do a
> > symlink to the "standard" htdocs/packages location, or if they don't want
> > to use symlinks, they should probably use the htdocs hierarchy that's
> > presented to them.
> I think you're underestimating the power of httpd.conf. Take a look again
> at my original message for some of the havoc people can play with
> mod_rewrite, and that was light examples. Non-standard content handlers,
> smarter mime-type guessing and all sort of things come in.
> You need to carve out a URL namespace for each application, and make
> sure (by having a master httpd.conf that the user must not touch (i.e.,
> it's not considered a config file) which includes first the user config
> file and then the Debian config files)
> I haven't even started talking about Apache virtual host, which add
> another layer of complication to this thing. Oh, and ports too.
> And IP-based virtual hosts.
Let alone those who do not use apache.
Christopher F. Miller, Publisher email@example.com
MaineStreet Communications, Inc 208 Portland Road, Gray, ME 04039
Database publishing, e-commerce, office/internet integration, Debian linux.