If it only happens sporadically for some users it's probably caused by an ActionController::InvalidAuthenticityToken which again is caused by disabled cookies in the users browser.
You can handle these errors by adding this to your application controller: rescue_from ActionController::InvalidAuthenticityToken, :with => :handle_token_issues def handle_token_issues redirect_to(somewhere) #redirect to page for handling this issue end If this were a problem caused by wrong protect_from_forgery settings I think it would also show up in development. -- Posted via http://www.ruby-forum.com/. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
