On Thu, Mar 26, 2009 at 6:55 PM, Sudhir <sud...@gmail.com> wrote: > > After upgrading to Rails 2.3.2 I am now experimenting with Rails > caching. I have cache enabled for one action in a few controllers. > This seems to work until I restart the server. > > After restart, I get Invalid Authenticity token errors on POSTS from > pages that were previously cached. I've tried clearing the browser > cookies and cache and the problem does not appear to be on the browser > side. > > I think the default cache store is Memory. I don't see any cached > files on the disk. > > I can clear the problem by visiting an uncached page on my application > and POSTing from there. My cache sweeper expires the cache in that > case. After this, everything works since I expire all cached URL's. > > Is there a way to definitely clear the Rails cache on server restart? >
The following should work for you: rake tmp:cache:clear Thus, you might want to invoke the above when you start/restart your server. > > Also, please confirm that the default cache store is memory. I had > assumed that the memory cache would clear automatically on server > restart. Maybe my assumptions are not correct. > > Thanks. > > In production, the default global cache is mem_cache_store. Good luck, -Conrad > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---