"Train the user not to do that" is a cop out. If an application doesn't work the way users expect, it's a problem with the application, not the user. That's usability 101.
If the user shouldn't bookmark the login page, they shouldn't ever be exposed to the URI for the login page. That makes it impossible to bookmark. The only URI that the user should see is the URI for the protected resource. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 03, 2001 6:23 PM > To: [EMAIL PROTECTED] > Subject: DO NOT REPLY [Bug 3839] - Problem bookmarking login page > > > 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 > > [EMAIL PROTECTED] changed: > > What |Removed |Added > -------------------------------------------------------------- > -------------- > Status|REOPENED |RESOLVED > Resolution| |WONTFIX > > > > ------- Additional Comments From [EMAIL PROTECTED] > 2001-10-03 15:23 ------- > The fact that you hd the same problems under WebLogic also > should have given you > a hint that you might be mis-using this functionality :-). > > Although the form login page (and form error page) are > physically contained in > your web application archive, they should not be hyperlinked > to by any of your > app's pages. Most particularly, it should *not* be your welcome page. > > If you (temporarily) switch your app to use BASIC > authentication instead, it > should still work correctly - and there is no possibility to > bookmark the login > page because there is no such thing. If your app doesn't > work in this scenario, > then you should modify it so that it can. > > If you don't, then you're going to be dependent on > non-portable behavior of > whatever container vendor happens to allow this technique to > work - the spec > doesn't require it. > <><><><><><><><><><><><><><><><><><><><><>This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail. <><><><><><><><><><><><><><><><><><><><><>
