Oops, I just realized that javascript code executing always on client's 
browser, and any request will have 'REMOTE_ADDR' = client's IP. Thus, there is 
only approach to use some kind of authenticity_token.



On 24.07.2012, at 23:29, Hassan Schroeder wrote:

> On Tue, Jul 24, 2012 at 12:09 PM, Valery Kvon <adda...@gmail.com> wrote:
>> If the javascript runtime could do it… :)
> 
> JavaScript? Is this executing on the client or on the server?
> 
> -- 
> Hassan Schroeder ------------------------ hassan.schroe...@gmail.com
> http://about.me/hassanschroeder
> twitter: @hassan
> 
> -- 
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to