Thanks Holger, that indeed explains it. So basically, this is an Internet Explorer issue, that cannot easily be solved by web authors. Oh, one more question about this, do you know if this behaviour has anything to do with choosing 'get' or 'post' as the 'method' for sending the form?
-Stijn ----- Original Message ----- From: "Holger Dewes" <[EMAIL PROTECTED]> To: "'Jetspeed Users List'" <[EMAIL PROTECTED]> Sent: Monday, February 16, 2004 11:36 AM Subject: RE: Can 'Warning: page expired' be prevented? > -----Original Message----- > From: Stijn de Witt [mailto:[EMAIL PROTECTED] > Sent: Sunday, February 15, 2004 2:14 PM > To: Jetspeed Users List > Subject: Re: Can 'Warning: page expired' be prevented? > > > But why is it happening? Does Jetspeed need to send > parameters along on every request? IE seems to think that > there is formdata being submitted... Do you get the message when not using a form? I have only noticed it when a form was used (which happens quite a lot in my portlets). IE, apparently, then does not want to send the request again without asking the user first. > > I really want to solve this, because the back button is the > most-used navigational instrument on a browser (about 40% of > 'clicks') if you don't count links on pages. > Yes, but it is almost always a problem with stateful web applications, where every request has a side-effect on the server. -- Holger Dewes > -Stijn > > > ----- Original Message ----- > From: "Holger Dewes" <[EMAIL PROTECTED]> > To: "'Jetspeed Users List'" <[EMAIL PROTECTED]> > Sent: Friday, February 13, 2004 4:36 PM > Subject: RE: Can 'Warning: page expired' be prevented? > > > > -----Original Message----- > > From: Stijn de Witt [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, February 11, 2004 7:43 PM > > To: Jetspeed Users List > > Subject: Can 'Warning: page expired' be prevented? > > > > > > I have been noticing that jetspeed + MSIE's Back button > tends to giva > > a page expired warning...Is there a way to circumvent this? > > I had problems with that too, but alas found no solution. You > can allow caching by setting http.lifetime to -1, but then > Jetspeed won't work properly, because e.g. by clicking a link > to change to a different pane, IE will call the cache and > Jetspeed won't get the request and the current pane will > remain the same which results in weird behaviour. > Unfortunately, I found no way to configure IE in a way so it > will automatically dispatch the request again without asking first. > > I heard some people use history.replace() for all links or > disable the back button using Javascript, but that's quite > nasty IMHO :-) > > -- > Holger Dewes > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
