Nick Kew wrote:
my application is a cgi script, by setting the environment variable REMOTE_USER the application can make use of that, in my case there is no direct need for r->user. unfortunately since the remote_user is usable by my cgi script, it does not really auth the network users to apache, thus requiring me to use allow from network; satisfy any.André Warnier wrote:.. and to explicit the question even more :Deep down in Apache's "request record" for the current request, there is a field which contains the authenticated user-id for this request, thus available to any other Apache module (not only to cgi scripts). I have a doubt that merely setting the "Apache variable" REMOTE_USER would auto-magically set this field.That's r->user, which is presented to CGI (and things that adopt or "embrace and extend" CGI) as REMOTE_USER. Most applications (except authz modules) use REMOTE_USER, so won't need r->user. Is your application implemented a a module or modules, or is it external to the server?
For my current needs this does work well for me and see no problem with it. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|