|Summary:||mod_dir does not manage correctly the user (r->user) in the response handler|
|Product:||Apache httpd-2||Reporter:||titetluc <titetluc>|
|Component:||mod_dir||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
|Attachments:||adds "r->user = rr->user" to ap_internal_fast_redirect|
Description titetluc 2008-06-27 05:16:08 UTC
I have a problem retrieving the user identity (r->user) in a specific configuration (using mod_perl). I sent a mail on the mod_perl mailing list to verify if the pb came from mod_perl. The thread can be found here: http://www.gossamer-threads.com/lists/modperl/modperl/97533 Torsten Foertsch (thanks to him) configured a basic httpd configuration to locate the problem. It seems that mod_dir does not work properly. All the story in the previous link !
Comment 1 Torsten F 2008-06-27 08:05:58 UTC
I have verified it without mod_perl with apache 2.2.9: DirectoryIndex index.shtml Options Includes Indexes AddType text/html .shtml AddOutputFilter INCLUDES .shtml <Location /index.shtml> Require valid-user AuthType basic AuthName "Something very secret" AuthUserFile /path/to/htpasswd </Location> My index.shtml reads: <html> <body> <h1>Hello <!--#echo var="REMOTE_USER" --></h1> <pre> <!--#printenv --> </pre> </body> </html> If /index.shtml is requested all works normal. If only / is requested I get the password prompt. Then it shows the page but the REMOTE_USER variable is unset. This variable is r->user.
Comment 2 Torsten F 2008-06-27 08:28:47 UTC
Created attachment 22189 [details] adds "r->user = rr->user" to ap_internal_fast_redirect ap_internal_fast_redirect looks to me like a very ugly hack. Its name suggests that it does an internal redirect but it doesn't. It simply destroyes the current main request and overrides it with the other. Why is it used instead of ap_run_sub_req?
Comment 3 William A. Rowe Jr. 2018-11-07 21:09:15 UTC
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.