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=3839>. 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=3839 Problem bookmarking login page ------- Additional Comments From [EMAIL PROTECTED] 2002-06-14 07:51 ------- That workaround is dangerous. In some browsers (like Opera) referrer logging can be disabled, in which case you have an endless loop... Two other suggestions for a workaround (but probably non-portable): - Test isNew() on the Session object. For form-based login, the container needs to store the context of the original call somewhere. I pretty sure that tomcat uses the session object for this (though it will be hidden from the webapp) - Put the login page itself in the protected area. I believe Tomcat 4 allows this. In the login page you can then put code to test if the user is already logged in. If he is, he got there because he bookmarked the login page, got the 'container' login page, logged in and was redirected to the 'application' page (that happens to be the same). In that case, redirect to the application default page. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
