Hi,
the header forcing browser not cache the page are:
Pragma: No-cache
Cache-Control: no-cache,no-store,max-age=0
Expires: 1
Jirka
PS: It makes problems with downloading file (attachments) in IE via HTTPS, so
you have change header for attachemnt
downloding for IE to:
Cache-Control: max-age
I usually solve (1) with a "Flow Synchronizer". Search this list, and see:
http://www.junlu.com/msg/85270.html
For (2) I think the only safe way is to close the window. Perhaps you can
ask the user to do this, and then do it via a timer in javascript anyway.
Using forms might force a refresh whe
gmail used to disable the back button. Now they've hacked it to do
the 'correct' thing. It is apparently browser dependent, however, as
the back button still sends you to the previous SITE when using gmail
in Safari. In firefox, they must be trapping the back button and
sending an ajax request.
How does Tacos do it? I see the @DirtyFormWarning won't let you click
the back button if you changed the form (It will popup a warning
instead). I believe they use javascript with window.onbeforeunload
event. Here is a link:
http://www.webreference.com/dhtml/diner/beforeunload/bunload4.html
An
Mats Henricson a écrit :
2. After a logout. We don't want our users to be able to use the back
button
to see the
last page, from which he clicked the "Log out" link. We know that going
somewhere
from that brought back page would lead the user to the login page, but
none the less,
it would
throw a RedirectException ?
You could optionally also probably remove items from their browser
history via javaxscript (I think? ) , but the redirect is probably
easiest.
On 11/29/06, Mats Henricson <[EMAIL PROTECTED]> wrote:
This may be elementary, but we have two cases where we don't want our
