It seems to be a workaround,
I think this depends on the client.
Maybe one user deactivates javascript,
the other user comes with the exotic browser lynx or WML ... a.s.o. :-)
The easiest solution is to set page caching either by sending HTTP
> headers with a servlet response:
> response.setDateHeader("Expires", -1);
> response.setHeader("Cache-Control", "no-store, no-cache,
> must-revalidate, max-stale=0, max-age=0, post-check=0, pre-check=0");
> response.setHeader("Pragma","no-cache");
> or adding equivalent meta tags in the page's head section:
> <meta http-equiv="Expires" content="0">
> <meta http-equiv="Cache-Control" content="no-store, no-cache,
> must-revalidate, max-stale=0, max-age=0, post-check=0, pre-check=0">
> <meta http-equiv="Pragma" content="no-cache">
>
> To completely block "back" action, you should also add a JavaScript call
> in the head section:
> <script>javascript:window.history.forward(1);</script>
> This should work, I hope.
>
> I'm not sure if meta tags are really equivalent to sending headers (they
> should be as far as I know). I've tested it with some simple servlet and
> they worked different from headers :/ Maybe I made some mistake, I don't
> know...
>
> --
> pozdrawiam,
> Jacek Wislicki
>
> [EMAIL PROTECTED]
> tel.: +48 502 408 444
> gg: 2540358
> skype: jacek_wislicki
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
