i think we could just reuse that max_redirects...
i have no idea, but this does cause some issues. see #12

Revert "Bug fix - Using jRuby 1.7.16 in 1.9 mode causes Encoding::CompatibilityError - incompatible encoding regexp match (ASCII-8BIT regexp with UTF-8 string). So force encoding for all regexp to use utf-8."

This reverts commit ac00e89ec9c5294f0648e03f48afdbeb7a871f6a.

Conflicts:
	lib/rest-core/patch/rest-client.rb
leave a space
RC::Cache: fix cache hit log
so that we properly log and cache redirect
now we only support >1.9.2
some logs might not need a duration
so really handle errors in the client instead of ErrorHandler

this could be a radical change that it would raise the exception
from the client instead of from ErrorHandler. now ErrorHandler
only tries to create the error rather than doing both.

this means that clients without ErrorHandler would now raise
exceptions! this should fix the confusion and inconsistent
problem mentioned in #6.

the intention for this change was all for creating RC::Retry,
which could retry the request upon errors. if we raise the exception
from ErrorHandler, then we have no chance to catch the error
before it's raised. this should make RC::Retry much easier to
implement.

hope this won't break too much code!