Re: [us...@httpd] accessing REMOTE_USER through an Apache proxy

2009-10-30 Thread Devin Bougie
On Oct 30, 2009, at 12:49 PM, André Warnier wrote: Glad to have been of help. One more nitpick however, below, lest you remain partly confused. Yes, indeed. I was confused by the "Same as the value of the CGI variable REMOTE_USER." statement in the HttpServletRequest.getRemoteUser javadoc,

Re: [us...@httpd] accessing REMOTE_USER through an Apache proxy

2009-10-30 Thread André Warnier
Hi. Glad to have been of help. One more nitpick however, below, lest you remain partly confused. Devin Bougie wrote: ... With the latest posted configuration, I am able to see the REMOTE_USER HTTP header from the backend GlassFish Web Application (using HttpServletRequest.getHeader("REMOTE_USE

Re: [us...@httpd] accessing REMOTE_USER through an Apache proxy

2009-10-30 Thread Devin Bougie
Hi André, Thank you very much for another thorough explanation. This certainly does help clear up my confusion. With the latest posted configuration, I am able to see the REMOTE_USER HTTP header from the backend GlassFish Web Application (using HttpServletRequest.getHeader ("REMOTE_USER"

Re: [us...@httpd] accessing REMOTE_USER through an Apache proxy

2009-10-29 Thread André Warnier
Devin, I still have some lingering doubt about whether there is not a confusion somewhere between - the Apache process's environment values (what it gets in its own environment when it starts up) - the Apache "internal environment variables" (set internally by Apache, for Apache only, during o

Re: [us...@httpd] accessing REMOTE_USER through an Apache proxy

2009-10-29 Thread Devin Bougie
I have tried a different approach by moving the RewriteRules into the Location directive. With this configuration, the HTTP_REMOTE_USER variable is set and visible by the backend script and application. However, REMOTE_USER is still blank. Here is the alternate configuration: --

Re: [us...@httpd] accessing REMOTE_USER through an Apache proxy

2009-10-28 Thread Devin Bougie
Hi André, Thank you very much for your time and explanation. For what it's worth, I have tried inserting a RewriteCond to make sure the proxy only occurs when REMOTE_USER is set. This cleaned up the rewrite.log file a bit, but the script is still not able to see REMOTE_USER. Here is ou

Re: [us...@httpd] accessing REMOTE_USER through an Apache proxy

2009-10-28 Thread André Warnier
Devin Bougie wrote: ... Hi. I'll give you my interpretation, after looking at the log, not really at the configuration. I think the confusion may be about when and where, things happen exactly. And it is not really helped by your choice to proxy from your server to itself.. If you examine

[us...@httpd] accessing REMOTE_USER through an Apache proxy

2009-10-28 Thread Devin Bougie
We proxy connections trough Apache to GlassFish Web Applications, and would like to give those applications access to the http REMOTE_USER variable. To make sure this is not related to GlassFish, I have created a very basic test script. The kerberos authentication and Apache proxy work pr