You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/01/01 22:35:24 UTC
DO NOT REPLY [Bug 5647] New: -
AJP13 connector will not pass authentication requests
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=5647>.
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=5647
AJP13 connector will not pass authentication requests
Summary: AJP13 connector will not pass authentication requests
Product: Tomcat 4
Version: 4.0.1 Final
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: AJP Connector
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: rasand@attglobal.net
Hi all- I've encountered a potential bug in Tomcat 4.0's AJP13 listener. I
have a default installtion of Apache 1.3.22, mod_jk, and Tomcat 4.0.1. I have
duplicated this environment on both Windows 2000 and Linux. mod_jk is talking
to Tomcat via ajp13. Tomcat is (as default) listening on 8080 for its HTTP
interface and on 8009 for ajp13.
The problem is this: when I access to Tomcat manager application through
Apache+mod_jk, i.e. http://myserver/manager/list, I get properly challenged to
log in, but my username and password never work, and Tomcat eventually says I am
unauthorized. If I then access the same resource directly through Tomcat,
i.e. http://myserver:8080/manager/list, I get access with no problem.
The problem could be in mod_jk, although I suspect it may lie in Tomcat's
ajp13 listener (simply because mod_jk is older and more widely used, whereas
Tomcat 4 is newer).
Please let me know if this is a bug, and if I can assist in any way.
Thanks!
Best regards,
Richard
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>