Content-Length: handle body w/ UTF8 characters for Ruby 1.9+ to avoid Rack::Lint::LintError #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks to cloudhead/toto#93, I have uncovered why our Rails application that uses stopwatch was producing
Rack::Lint::LintError
s, e.g.:This is a result of how Ruby handles lengths of UTF8 strings differently between 1.8 and 1.9.
This pull request uses
String#bytesize()
ifbody
responds to it, otherwise falls back toString#length
and eliminates theseRack::Lint::LintError
s in our Rails app.The stopwatch gem is very useful for Rails application development, and we have been using it for many years, thank you!