Hey Scott, I used a good recipe from the Rails Recipes book:
using map.connect '*path', :controller => "fail" as last line of routes.rb files and http://gist.github.com/244131 I can always have a the situation under control and I don't write too much log.. Some days I collect 10,000 weird requests.. Script Kiddies! oh, it's a 'few years old' rails code, let's ignore parts like: fail.count = 1 + fail.count fail.save ;) > I find tons of > > ActionController::RoutingError (No route matches ... > > entries, including > > ActionController::RoutingError (No route matches "/admin/default.asp" > > which means some bot is banging on the door looking for a weakness. > > 641 carts have been created in the last half hour with calls like > > Processing ProductsController#shipping_calculator > > which apparently creates a cart. > > Is this typical? Any simple way to weed out the junk from the log? > How about my plan for moving the document root to the new code > location? Should I just move it and restart the server and hope no > glitches occur (and no sales are lost)? > > Thanks again, what an adventure, > > Scott -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
