Ruby on Rails

On Wed, Jan 23, 2013 at 1:23 PM, Robert Walker <lists@ruby-forum.com> wrote:
> Michiel Sikkes wrote in post #1093276:
>> I am running a Rails 4 app in semi-production and I constantly get
>> exceptions from crawler bots that use a HEAD HTTP method, which causes
>> the
>> CSRF protection to kick in.
>>
>> Shouldn't HEAD requests normally be handled like GET requests?
>
> According to the Rails Guide it seems apparent that only GET request are
> assumed to be safe.
>
> http://guides.rubyonrails.org/security.html#csrf-countermeasures
> ---------------------------
> 3.1 CSRF Countermeasures
> — First, as is required by the W3C, use GET and POST appropriately.
> Secondly, a security token in non-GET requests will protect your
> application from CSRF.
> ---------------------------
>
> This document may be oversimplified, but judging by your question I'd
> say it works pretty much as described.

HEAD requests should not be CSRF protected, sounds like a bug needs to
be filed to me.

--
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 rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.