Currently the UserDir directive support various schemes like: * UserDir public_html -> ~bar/public_html/one/two.html * UserDir /usr/web -> /usr/web/bar/one/two.html * UserDir /home/*/www -> /home/bar/www/one/two.html Each of them having different advantages. The last two have the major advantage, that no local user has to be present on the web server machine to rewrite the requests. Unfortunately, those schemes do not offer a flexible rewrite policy. In scenarios with a lot of different users, home directories are often separated in different parent directories named by the first letter of the username, e.g. /home/b/bar. It would be really helpful to have a configuration rule to define such UserDir rewrite. For example: * UserDir /home/_/*/ -> /home/b/bar/one/two.html Thanks for you work! sandoz
Since '_' is a valid POSIX filename character, it is NOT a good idea to use it in such a scheme. One would rather use a scheme like the following: * UserDir /home/?/*/ -> /home/b/bar/one/two.html JFTR, sandoz
Created attachment 22188 [details] Patch for mod_userdir.c to add a new UserDir conf scheme. This patch adds a new configuration scheme to the UserDir directive. * UserDir /home/?/*/public_html -> /home/a/anabel/public_html This scheme makes it possible to subdivide the /home directory into directories named by the first letter of the usernames, e.g. /home/a/anabel, /home/b/bob, etc. For computational simplicity, that scheme allows only such configurations, where the '?' sign comes before the '*' sign.
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.