I was doing Request profiling like Ryan Bates showed on railscasts (http://railscasts.com/episodes/98-request-profiling) and I wanted to profile some update action.
I've prepared a script: http://pastie.org/267554 After running request profiler I saw InvalidAuthenticityToken error. I disabled it and then realized that user is not authorized while profiling. So I've skipped login_required and authorization. But... current_user data is needed in some of the actions. I definetely have to provide valid user. Auth token isn't important, but still, disabling it on while profiling isn't the best solution How to handle it the rails way? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
