ERROR Rack::Lint::LintError

[kris]

Hi, was trying to use rack-throttle on Interval 3sec, and it works just fine until you hit the threshold, in which it errors out with:

[2011-02-04 21:00:37] ERROR Rack::Lint::LintError: Response body must respond to each
/Users/kris/.rvm/gems/ruby-1.9.2-p136@rails3/gems/rack-1.2.1/lib/rack/lint.rb:19:in assert' /Users/kris/.rvm/gems/ruby-1.9.2-p136@rails3/gems/rack-1.2.1/lib/rack/lint.rb:513:ineach'
/Users/kris/.rvm/gems/ruby-1.9.2-p136@rails3/gems/rack-1.2.1/lib/rack/handler/webrick.rb:64:in service' /Users/kris/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/webrick/httpserver.rb:111:inservice'
/Users/kris/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/webrick/httpserver.rb:70:in run' /Users/kris/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/webrick/server.rb:183:inblock in start_thread'

[basayel]

I am facing the same problem .. Any luck with that ?

[bensomers]

This is actually the same bug as issues #2 and #6. The Rack standard dictates that a response body should respond to #each; It's because Limiter#rate_limit_exceeded is returning its response as a String, which responded to #each in ruby 1.8 but does not in 1.9. The correct fix is to wrap the response body in an array, as in 02297be.

You should try using one of the forks, most of them incorporate this fix or have made it independently. Mainline appears pretty strongly to be unmaintained. I'll obviously plug for mine (https://github.com/bensomers/improved-rack-throttle), but there are several that would work.

(Incidentally, my commit referencing this issue is an example of github's Markdown being overly aggressive. I actually just wanted a numbered list in that commit message, not specific issue references.)

[basayel]

Thanks so much @bensomers I tried the improved-rack-throttle and it did the job .. I really hope the authors respond to the pull requests to have a single reference. The last commit had been 2 years ago

[FreekingDean]

Cleaning up old Issues, this should be fixed as of #17