>Your login page has a form with ACTION="/servlet/LoginServlet". When the
>user submits the form, the user's browser goes to the page
>"/servlet/LoginServlet". The servlet does it's work, and forwards to some
>other page, let's say your main menu page, but the user still sees the url
>of "/servlet/LoginServlet". So if they were to bookmark this new page,
>they'd really be bookmarking the servlet.
>So then you'd need to write code in the servlet to handle this possibility
>and blah, blah, blah. I've taken to avoiding servlets and forward() all
>together to avoid this.
Actually, the converse is much more likely to be the case. That is, a user
tries to access "/servlet/ShowPrivilegedInfo", which checks the session and
possibly redirects (invisibly) to a login screen. If the user bookmarks,
it will behave as expected, showing the page or jumping to the login screen
if necessary. I always use such an architecture, and it functions very
naturally and smoothly.
The one place you might have some trouble is if the servlet depends on
POSTed form data to decide which page to redirect to -- but this would be
true in any case.
-Ben
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
