* Drop support for Ruby 1.9.2, which no-one should be using any more.
* Constraint gem versions for Ruby 1.9.3
* Drop support for Ruby 1.8.7. Many dependencies have dropped support for it.
* Remove conditionals checking for Ruby 1.8.7
* Document Ruby version dependency
Some servers such as Exchange 2010 don't like that there isn't a space
after a semicolon separator in the Content-Type request header. Since
Net::HTTPHeader#set_content_type adds the space, as well as it appearing
in the examples of RFC 2616, this follows suit and adds a space which
should help bad-behaving servers and not harm others.
In Ruby 1.8, when you are operating with unicode encoding, \w includes
UTF-8 characters such as ☃. Faraday therefore does not escape these
correctly.
Closes#245
These middleware now pay attention to "Content-Type" of the request.
Each will only encode the body if the content-type value matches.
When a body is present but no Content-Type, the middleware higher on
the stack will use its encoding.
This makes it possible to keep both middlewares on the stack and choose
encoding type by Content-Type switching.
