anchor.diff:  
   == Using HTTPS
   
  -Vert.x web client can be configured to use HTTPS in exactly the same way as the Vert.x {@link io.vertx.core.http.HttpClient}.
  +Vert.x Web Client can be configured to use HTTPS in exactly the same way as the Vert.x {@link io.vertx.core.http.HttpClient}.
   
   You can specify the behavior per request
   
  
positive.code: * unified error handling
  * form submissions
  
  The web client does not deprecate the Vert.x Core {@link io.vertx.core.http.HttpClient}, indeed it is based on
  this client and inherits its configuration and great features like pooling, HTTP/2 support, pipelining support, etc...
  The {@link io.vertx.core.http.HttpClient} should be used when fine grained control over the HTTP
  requests/responses is necessary.
  
  The web client does not provide a WebSocket API, the Vert.x Core {@link io.vertx.core.http.HttpClient} should
  be used. It also does not handle cookies at the moment.
  
  == Using the web client
  
  To use Vert.x Web Client, add the following dependency to the _dependencies_ section of your build descriptor:
  
  
negative.code: Vert.x Web Client uses the API from Vert.x core, so it's well worth getting familiar with the basic concepts of using
  {@link io.vertx.core.http.HttpClient} using Vert.x core, if you're not already.
  
  == Creating a Web Client
  
  You create an {@link io.vertx.ext.web.client.WebClient} instance with default options as follows
  
  