www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From emery ford <emery_f...@bigfoot.com>
Subject suexec/3357: unable to specify doc_root to be other than $(datadir)/htdocs for suEXEC
Date Fri, 06 Nov 1998 18:16:45 GMT

>Number:         3357
>Category:       suexec
>Synopsis:       unable to specify doc_root to be other than $(datadir)/htdocs for suEXEC
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Nov  6 10:20:01 PST 1998
>Originator:     emery_ford@bigfoot.com
>Release:        1.3.3
solaris 2.6
SunOS sunweb 5.6 Generic_105181-03 sun4u sparc
gcc version 2.8.1
with configure you can specify a datadir=DIR the doc root becomes $(datadir)/htdocs.  

The DocumentRoot directive in the conf files doesn't change the docroot, at least for suEXEC
purposes of determining whether a requested directory is within the server's webspace.

Why does this matter?  I am trying to keep my directory structure as flat as possible.

This is simplified view of the  way I need to set up multiple virtual hosts presently for
suEXEC capability:


...and this is the way I think it should be.



1. allow configuration command line option for specifying datadir to include the currently
mandatory 'htdocs' directory. DOC_ROOT=$(datadir) rather than DOC_ROOT=$(datadir)/htdocs
2. Or, allow configuration command line  option to specify what 'htdocs' should be, allowing
it to be null.
3. Allow the configuration files to specify the DocumentRoot for suEXEC purposes.

Thanks for all your help. You guys are great!  -Emery
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]

View raw message