Folks,
> I was wondering on this topic for a long time and found out that no you
> cannot control the BACK functionality of the browser. (Just the same as you
> cannot hide the source code viewing and possible misuse by users).
>
> As you said, however, you can make sure that these actions if taken, dont
> turn out to be harmful to the servlet application. Thats a whole new issue
> one must take care of while designing ...
>
> The *smart* pages which overcome the BACK operation put up a smart step in
> between the two pages.
>
> 1 --> smart page --> 2.
>
> The smart page is a simple forwarding page which takes the user
> *immediately* to the page 2. So form page 2 you do a back .. you are forced
> to page 2 again. A kinda simulation of BACK being trapped ;-)
This brings up an interesting point; what happens if you back up
to a page generated by a POST operation? The standard behavior is to
ask the user if they want to repost the data. How do you disable this
if you want the form not to be cached? Make the form page no-cache?
Steven J. Owens
[EMAIL PROTECTED]
[EMAIL PROTECTED]
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
