-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
Rainer Jung wrote:
> We know that mod_jk forwards the info about the
> protocol used by Apache when accepting the original request and this
> info is handled by Tomcats security-constraint the same was, as if
> Tomcat had created it on its own
Christopher Schultz wrote:
Omar Nafees wrote:
1) request.getRemoteUser() only works on the "entry-point" servlet (e.g.
index.jsp) - it doesn't work if you forward immediately to another page.
It seems strange that Tomcat doesn't keep remote user around for later
use and forces me to keep it arou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Omar,
Omar Nafees wrote:
> 1) request.getRemoteUser() only works on the "entry-point" servlet (e.g.
> index.jsp) - it doesn't work if you forward immediately to another page.
> It seems strange that Tomcat doesn't keep remote user around for later
> u
Hi,
I recently posted under the thread "Apache authentication information
(remoteuser) not visible in Tomcat" and I am grateful to all that
responded with useful comments.
I learned the following about how Tomcat treats authentication
information received from Apache via AJP headers (mod_jk)
