This manual is not clear for me. Actually it says about apache mod_cache configuration. But I am not using apache. Only jetty is used. ________________________________________ From: news [[email protected]] On Behalf Of Andreas Hartmann [[email protected]] Sent: Tuesday, July 28, 2009 5:40 AM To: [email protected] Subject: Re: back button + continuation id problem
Hi Oleg, Oleg Barmin schrieb: > Could you please help to configure no cache headers for the login page? this page pretty much sums up what you need to know: http://wiki.apache.org/cocoon/ControllingModCache HTH, -- Andreas > > Best regards, > Oleg Barmin. > ________________________________________ > From: news [[email protected]] On Behalf Of Andreas Hartmann > [[email protected]] > Sent: Saturday, July 25, 2009 5:47 AM > To: [email protected] > Subject: Re: back button + continuation id problem > > Oleg Barmin schrieb: >> We can not deny to the users to use back button. So that is why we >> need to handle this situation in a some way. > > I think the only sensible way is to prevent the browser (and any other > caches) to cache responses containing continuation IDs. I'm not sure, > though, about the most reliable way to do this. I guess you need a > combination of > > Headers: > > Pragma: no-cache (HTTP 1.0) > Cache-control: no-cache, no-store (HTTP 1.1) > Expires: -1 > > Meta data: > > <meta http-equiv=”Pragma” content=”no-cache”> > <meta http-equiv=”Cache-Control” content=”no-cache”> > <meta http-equiv=”Expires” content=”-1″> > > -- Andreas > > >> ________________________________________ From: Richard Frovarp >> [[email protected]] Sent: Friday, July 24, 2009 1:24 PM To: >> [email protected] Subject: Re: back button + continuation id >> problem >> >> Oleg Barmin wrote: >>> Scenario: 1) Log in. 2) Press back button in the browser. 3) Try >>> log in again. >>> >>> >>> How to handle this situation? I am thinking about something like >>> expiration page. Is this correct? >>> >>> Best regards, Oleg Barmin. >>> >> Don't hit the back button. Most any work inside of Lenya (or most web >> applications) does not respond well to use of the back button. >> >> What's going on is there is a one time use id (the continuation) that >> is associated with the form. You submit the form and that one time >> use id is used up. Hitting back results in the browser showing the >> form without a valid continuation id. Since back typically pulls from >> the cache, there is nothing that can be done to cause a new >> continuation to be generated for the form. A reload from the server >> will provide a new continuation. >> >> Richard >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] For >> additional commands, e-mail: [email protected] > > > -- > Andreas Hartmann, CTO > BeCompany GmbH > http://www.becompany.ch > Tel.: +41 (0) 43 818 57 01 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] -- Andreas Hartmann, CTO BeCompany GmbH http://www.becompany.ch Tel.: +41 (0) 43 818 57 01 --------------------------------------------------------------------- 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]
