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=25055>. 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=25055 getRemoteUser() returns null (again) ------- Additional Comments From [EMAIL PROTECTED] 2003-12-01 16:23 ------- Remy, thanks for the response. First to your comments I had tried the default connector at the beginning, and I also tried to put tomcatAuthentication=false inside the connector element. The same results.... BUT I just realised that the problem is much deeper and may be a result from a wrong interpretation from my part. As I just saw, a call to http://myhostname/myprotecteddir/ _does_ correctly return the username, whereas http://myhostname/myprotecteddir/index.jsp does _not_ return the username and even _does_ _not_ ask for a login/password at all. I understand that in the second case apache sends the request to tomcat as it detects the *.jsp extension, without checking the existence of the .htaccess file. This is a different behaviour than I had with both tomcat 3.3 and 4.1.24 (both on apache 1.3.. I now use apache 2) My httpd.conf has a simple JkMount /*.jsp ajp13 JkMount /servlet/* ajp13 It doesn't seem a "LoadModule order" issue, as I tried to reverse the order of mod_jk with mod_auth So I'm stumped right now... is it supposed to work like this?? Then how can I protect all pages below a directory using apache's basic auth mechanism? Although this turns out to be a tomcat-user issue, I would appreciate a short answer if this is indeed the way it is supposed to work --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
