Please read for an updated status on RailsCasts:
Learn more or hide this
GitHub User: thelucid
Found the answer in the Edge Docs here: http://edgeapi.rubyonrails.org/classes/ActionController/RequestForgeryProtection.html#method-i-protect_against_forgery-3F
...others might benefit if this is included in the show notes.
In Rails 4 beta1, I'm getting a "HTTP/1.1 422 Unprocessable Entity" error when attempting a post request to an API. The controller is raising an ActionController::InvalidAuthenticityToken error.
Do I need to somehow disable request forgery protection for APIs?
This could work nicely with Mongoid to create custom fields in MongoDB.
p.s. loving the Pro and Revised episodes Ryan!