DO NOT REPLY [Bug 26229] - request.getRemoteUser() = null

[bu...@apache.org]

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=26229>.
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=26229

request.getRemoteUser() = null





------- Additional Comments From paul@boddie.org.uk  2004-02-13 08:34 -------
This isn't a browser-specific thing as far as I can see - I've tested with
Mozilla and IE.

Apache 1.3.29, JK2 2.0.2, Tomcat 4.1.29 all conspire (even with the
request.tomcatAuthentication=false setting in jk2.properties) to somehow pass on
the appropriate headers, yet the remoteUser just isn't available to applications
- in my case, that's a Cocoon 2.1.3 application, but the Cocoon stuff doesn't
seem to be at fault.

However, it all works fine in Tomcat 4.1.27, so I should imagine that something
changed between Tomcat releases and it all stopped working. Either that or the
Cocoon developers misunderstood some subtle aspect of the servlet specification,
but that doesn't seem likely to me.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org