Harold A. Gimenez wrote: > That's a great idea, until someone in the outside finds out about that > path/resource. You're opening up too much and scriptkiddies can get > happy attempting a DoS. Wondering if you handle that somehow (IP address > check or something)?
How about using HTTP basic authentication so only authorized clients can access the controller action? Which would be only your rake task. I haven't thought this through, It's just the first thing that came to mind. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
