depending on the substring, something optimized like grep is presumably going to be significantly faster than `lines.each do line.include? ... end`. How much that matters depends on how big your logfiles are
http://blog.burntsushi.net/ripgrep/#mechanics also this blog post about benchmarking grep implementations
for a 35MB logfile with 300k lines, grepping for 'foo' with 12 matches, ruby -e `STDIN.read.split("\n").each do |line| puts line if line.include? "foo" end` is ~1100ms real 600ms user, ruby -e `'STDIN.each do ... end` is ~600ms real 460ms user, and `grep -F` is ~130ms real 50ms user
so an ~order of magnitude difference for grep vs ruby loop with String#include?
if I have debian redmine installed in /usr/share/redmine, using debian rails 2.3, is the CVE-2013-0156 workaround just config/initializers/cve-2013-0156.rb: `ActionController::Base.param_parsers.delete(Mime::XML)`? How can I test if it worked?
I tried some `curl -v -H 'Content-type: text/xml' -X POST -d '...'` but not sure what kind of error I should be getting