You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/03/25 21:02:33 UTC
DO NOT REPLY [Bug 18337] New: -
AddModule order important within apache configure file
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18337>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18337
AddModule order important within apache configure file
Summary: AddModule order important within apache configure file
Product: Apache httpd-1.3
Version: 1.3.27
Platform: PC
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Documentation
AssignedTo: bugs@httpd.apache.org
ReportedBy: jjolly@mindless.com
There is no documentation (that I could find) indicating that the order of
AddModule statements within the configuration file.
This was apparent when attempting to use VirtualDocumentRoot and UserDir
operators. The idea configuration would be to have document roots specified by
the hostname, except where ~<uid> was used in the path. In this case, the
public_html directory specified by UserDir should take precidence.
In the initial configuration, AddModule mod_userdir.c preceeded AddModule
mod_vhost_alias.c. This caused all ~<uid> requests to be mapped to the
document root of the host. After swapping the two directives (mod_userdir.c
after mod_vhost_alias.c), the ~<uid> requests were successful as well as
virtual document root request.
Had this been documented in the AddModule reference, a couple of hours work
would have been saved.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org