All Versions
Latest Version
Avg Release Cycle
14 days
Latest Release

Changelog History
Page 1

  • v3.13.6 Changes

    • issue #424 Cannot use response.mapError with ByteResponse
  • v3.13.5 Changes

    • ๐Ÿš€ Bump httpasyncclient dependency to 4.1.5 for bug fixes.
  • v3.13.4 Changes

    • โž• Add ability to override all Headers with a map
  • v3.13.3 Changes

    • ๐Ÿ‘Œ Support a way to override Apache HttpClientBuilder options with the Client Builder. All Unirest configs are set first, then the consumer is called which allows consumers to override or add additional configs: java Unirest.config() .httpClient(ApacheClient.builder(c -> c.setMaxConnTotal(5000));
  • v3.13.2 Changes

    • ๐Ÿ‘ Allow using a MockResponse in the MockRequestBuilder
  • v3.13.1 Changes

    • โž• add some new features to MockClient
      • mockClient.reset() will clear any expectations
      • mockClient.defaultResponse() returns a default response expectation for when an explicit expectation was not matched
      • thenReturn(Supplier supplier) allows you to set the response body as a supplier to be invoked at request time.
  • v3.13.0 Changes

    • ๐Ÿ‘Œ Support InputStreams as bodies.
    • ๐Ÿ‘Œ Support ProgressMonitors for InputStream bodies
    • ๐Ÿคก Unirest-Mocks now includes a MockResponse and a MockConfig for use independent of the MockClient
  • v3.12.0 Changes

    • โฌ†๏ธ Bump GSON to 2.8.8
    • ๐Ÿ‘Œ Support honoring Retry-After headers on 429/529 for regular (not async) requests.
      • This feature will likely not make it to async until Unirest 4.
      • Can be enabled with Unirest.config().retryAfter(true);
      • Has a max re-try counter with a default of 10 which can be set with:
      • Unirest.config().retryAfter(true, maxNumberOfRetries);
      • ๐Ÿ”ฅ While Honoring The Retry-After header the thread will be blocked! ๐Ÿ”ฅ
      • It is highly recommend that this feature be used in conjunction with a circuit-breaking framework.
      • Let's say you have a web app that is making Unirest calls to downstream system X. You have many requests invoking this same service. If X starts to return 429's and Unirest is waiting on ALL of those requests. Unirest will quickly consume all your threads. At this time Unirest has no circuit-breaker of it's own to detect that this is happening. It will simply be happy to pause all of your threads forever.
  • v3.11.14 Changes

    • โฌ†๏ธ Bump GSON to 2.8.8
  • v3.11.13 Changes

    • โฌ†๏ธ Bump Jackson version in object-mapper-jackson to 2.12.4
    • โฌ†๏ธ Bump test and CI dependencies