What kiger was getting at is that the user can only see what is in their browser's cache - which is what they were allowed to see a second ago anyway... They won't be able to click any links, or perform any actions.
But regardless, what you really want is browser history management. Search google for javascript to destroy the browser history, or have some javascript that on page load performs an ajax request to check login status - this javascript will run again even on hitting the back button. But without Javascript I don't think it is possible - unless anyone knows of page headers that can instruct a browser not to cache at all? I haven't heard of such a thing. On Dec 5, 4:39 am, Joyce <[EMAIL PROTECTED]> wrote: > I see. Hopefully I can get what you mean by that. > > I will give it a shot. Thanks. > > On Dec 5, 2:31 am, "Chris Hartjes" <[EMAIL PROTECTED]> wrote: > > > On Dec 4, 2007 1:26 PM, Joyce <[EMAIL PROTECTED]> wrote: > > > > Thanks Chris, > > > > I will look through your tutorials. I am using CakePHP 1.1, can that > > > work? > > > The Auth component is not available in 1.2, but I believe you can use > > the Security component to do similar things. > > > -- > > Chris Hartjes > > > My motto for 2007: "Just build it, damnit!" > > > @TheKeyboard -http://www.littlehart.net/atthekeyboard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
