All Versions
35
Latest Version
Avg Release Cycle
179 days
Latest Release
1318 days ago

Changelog History
Page 4

  • v1.4.0 Changes

    • ⚠ Response is no more a String, and the mixin is replaced by an abstract_response, existing calls are redirected to response body with a warning.
    • enable repeated parameters RestClient.post 'http://example.com/resource', :param1 => ['one', 'two', 'three'], => :param2 => 'foo' (patch provided by Rodrigo Panachi)
    • 🛠 fixed the redirect code concerning relative path and query string combination (patch provided by Kevin Read)
    • 🚚 redirection code moved to Response so redirection can be customized using the block syntax
    • 0️⃣ only get and head redirections are now followed by default, as stated in the specification
    • added RestClient.add_before_execution_proc to hack the http request, like for oauth

    The response change may be breaking in rare cases.

  • v1.3.1 Changes

    • ➕ added compatibility to enable responses in exception to act like Net::HTTPResponse

  • v1.3.0 Changes

    • a block can be used to process a request's result, this enable to handle custom error codes or paththrought (design by Cyril Rohr)
    • ⚠ cleaner log API, add a warning for some cases but should be compatible
    • 👀 accept multiple "Set-Cookie" headers, see http://www.ietf.org/rfc/rfc2109.txt (patch provided by Cyril Rohr)
    • ✂ remove "Content-Length" and "Content-Type" headers when following a redirection (patch provided by haarts)
    • 👻 all http error codes have now a corresponding exception class and all of them contain the Reponse -> this means that the raised exception can be different
    • 🔄 changed "Content-Disposition: multipart/form-data" to "Content-Disposition: form-data" per RFC 2388 (patch provided by Kyle Crawford)

    👻 The only breaking change should be the exception classes, but as the new classes inherits from the existing ones, the breaking cases should be rare.

  • v1.2.0 Changes

    • formatting changed from tabs to spaces
    • logged requests now include generated headers
    • accept and content-type headers can now be specified using extentions: RestClient.post "http://example.com/resource", { 'x' => 1 }.to_json, :content_type => :json, :accept => :json
    • 📦 should be 1.1.1 but renamed to 1.2.0 because 1.1.X versions has already been packaged on Debian

  • v1.1.0 Changes

    All changes exept the last one should be fully compatible with the previous version.

    ⚡️ NOTE: due to a dependency problem and to the last change, heroku users should update their heroku gem to >= 1.5.3 to be able to use this version.