er javadoc, but you have again helped
explain that.
Thanks again,
Devin
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_USER")).
O
server is set up with mod_perl, I could give you a
Perl cgi-bin script which would show you the difference.
That's because under mod_perl, Perl cgi-bin scripts *can* ask Apache
for the original HTTP request headers.
Devin Bougie wrote:
I have tried a different approach by moving t
92.168.213.159 - dab66 [29/Oct/2009:11:04:47 --0400] [ourserver.com/sid#8885358][rid#971a7d0/initial
] (1) [per-dir /test/] go-ahead with proxy request proxy:http://
localhost/cgi-bin/test/remote.cgi [OK]
--
Any suggestions for passing REMOTE_USER through an Apache proxy would
be greatly app
e23fc8/initial] (2) forcing proxy-throughput with
http://localhost:38080/HelloWeb/UserServlet
... [rid#8e23fc8/initial] (1) go-ahead with proxy request proxy:http://
localhost:38080/HelloWeb/UserServlet [OK]
--
Any suggestions would be greatly appreciated.
Thank you again,
Devin
On Oct 28
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
