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=6531>. 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=6531 Request Dispatcher forward to j_security_check not working [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2002-02-19 02:24 ------- Applications that try to reference the "j_security_check" URL by any means are guaranteed to be non-portable, because the spec only defines this URL as being significant when the *container* sends back the form login page. In fact, that is the way that Tomcat 4 implements it, so trying to use a request dispatcher to forward control to this page is not going to work, because the URL doesn't exist at that point in time (hence the 404 error). An alternative approach would be to subclass one of the existing Realm implementations and make it do the encoding for you before calling the "real" authenticate() method in its superclass. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
