> -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf > Of James Salter > Sent: Tuesday, October 21, 2008 4:42 PM > To: [email protected] > Subject: [Rails] Re: Non-Ruby REST client for Ruby REST server > > > fervic wrote: > > I found out that what was not letting me do the POST/PUT's is: > > > > "protect_from_forgery" > > > > because of the authenticity token needed. > > > > Now I need to know if there's a workaround for this without having to > > stop using this method. > > > > > > Thanks! > > Hi, > > I came across this problem and the solution is quite simple. Bumping this > topic for other poor googling souls. > > Just put skip_before_filter :verify_authenticity_token in your controller. > > See the docs for ActionController::RequestForgeryProtection for more info; you > could also override that method instead if you wanted to do something specific > for non-verified clients. >
So does that leave the forgery protection in place for browser clients? Thanks! -Roy --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
