Version 3.0.9

• Bug fix for an race condition in WebSocket connection. Now onConnected callback is called before the CompletableFuture is completed. Both the onConnected and CompletableFuture is called on the netto io threads, so avoid blocking!

Version 3.0.8

• Added support for fetching http version as well as status reason from HttpResponse
• Added support for supplying what http verb should be used in HttpClient

Version 3.0.6

• Improved shutdown by waiting for all channels to close
• Fixed potential NPE
• Removed duplicate AttributeKey
• Added HttpClient.isStarted() method

Version 3.0.2

• Added support for redirects for websockets

Version 3.0.0

• Redesign of builder APIs.
  • The ResponseBodyConsumer have been moved from the execute method to the build method.
  • The HttpCallback have been moved from the execute method to the withHttpCallback method.
  • The NioCallback have been moved from the execute method to the withNioCallback method.
  • A few methods have been renamed to align them between the classes.
• Added support for websocket.
• Added support for building multipart uploads.
• Added support for upload progression callbacks through the withUploadCallback method.
• Fixed a bug in idle timeout handling.

Version 2.3.1

• Client is now waiting for ssl/tls handshake to complete before trying to push data

Version 2.3.0

• Changed to Java 8
• Future<FutureResult<T>> has been replaced with CompletableFuture<HttpResponse<T>> in BuiltClientRequest.
• The CompletableFuture.get() can now throw ExecutionException which contains the underlaying Exception (Before this exception could be fetched from the FutureResult).
• HttpClient.setConf has been deprecated and replaced with NettyHttpClientBuilder.setOption
• UriQueryBuilder.addParameter can now be chained.
• Netty 4.1 has been bumped to 4.1.15.Final.

Version 2.2.0

• Refactor of SseClient

Version 2.1.10

• Made it possible to specify custom executor to execute the callbacks on

Version 2.1.8

• Added method to HttpBody to supply the used encoding.
• Sending the used encoding in the content-type header