Hide Forgot
Description of problem: The default httpd.conf sets UserDir disabled, causing confusing results if trying to configure UserDir in an VirtualHost. there is no documented way to override dusabled for all users, even if UserDir enabled seem to work. UserDir enabled without listing explicit usernames it not a documented form of the directive however. It's inclear to me why UserDIr disabled is set explicit by default, as the default if UserDir is not set is to not provide UserDir functionality unless later configured in an VirtualHost. Note that UserDIr enable / disabled is a different configuration space from UserDir somepathname. Version-Release number of selected component (if applicable): httpd-2.2.21-1.fc16.x86_64 How reproducible: always Steps to Reproduce: 1. Add a VirtualHost with UserDir public_html without touching the default httpd.conf. 2. systemctl httpd restart 3. Actual results: /~username/ requests is not mapped by UserDir. Expected results: Mapped request. Additional info: Things do work as expected if the UserDir disabled directive is simply commented out in httpd.conf, leaving the directive completely unset by default.
Thanks for the report. This is fixed in 2.4. UserDir is disabled in the default configuration because otherwise it will confirm or deny the presence of a given username on the system to a remote user.
Quote from the 2.2 manual: "User directory substitution is not active by default in versions 2.1.4 and later. In earlier versions, UserDir public_html was assumed if no UserDir directive was present."