httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 25725] - SetEnvIf Remote_User in .htaccess file
Date Wed, 14 Jan 2004 00:11:10 GMT
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=25725>.
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=25725

SetEnvIf Remote_User in .htaccess file

wrowe@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|SetEnvIf Remote_User in     |SetEnvIf Remote_User in
                   |.htaccess file              |.htaccess file



------- Additional Comments From wrowe@apache.org  2004-01-14 00:11 -------
Your scenario is trivial without SetEnvIf

#.htaccess file (Linux/Apache 1.3.22)

AuthName 'My Protected Area' 
AuthType Basic 
AuthUserFile /home/var/etc/.htpasswd 

<Files "index.php"> 
require user admin1 
require user admin2 
</Files> 

<Files "jpg1.jpg"> 
 order deny,allow 
 deny from all 
 allow from admin1
</Files> 

<Files "jpg2.jpg"> 
 order deny,allow 
 deny from all 
 allow from admin2
</Files> 


But presuming thats not what you wanted, why aren't you using groups to control
access, which is far more trivial and won't suffer these problems.

Apache goes through about 22 different stages in assembling a request before
actually running it.  We could add the env processing to all these phases, but
the cost of doing so would be tremendous on server performance.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message