Request profiling - login and authenticity token

I was doing Request profiling like Ryan B. 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?

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs