anchor.diff:  * Connection #0 to host localhost left intact
   false* Closing connection #0
   --------------
  +
  +.Unknown status
  +[NOTE]
  +===============================
  +The `UNKNOWN` status exists to describe when a Neo4j instance is neither master nor slave. For example, the instance
  +could be transitioning between states (master to slave in a recovery scenario or slave being promoted to master in
  +the event of failure). If the UNKNOWN status is returned, the client should not treat the instance as a master or a
  +slave and should instead pick another instance in the cluster to use, wait for the instance to transit from the `UNKNOWN`
  +state, or undertake restorative action via systems admin.
  +===============================
positive.code: * +/db/manage/server/ha/master+
  * +/db/manage/server/ha/slave+
  
  To use them, just do an HTTP GET at either and you'll get back the following:
  
  .HA REST endpoint responses
  [options="header", cols="2m,<1,<2m,<2m"]
  
negative.code: | Endpoint                           | Instance State  | Returned Code  | Body text
  1.2+^.^| /db/manage/server/ha/master | Master          | 200 OK         | true
                                       | Slave           | 404 Not Found  | false
                                       | Unknown         | 404 Not Found  | UNKNOWN
  1.2+^.^| /db/manage/server/ha/slave  | Master          | 404 Not Found  | false
                                       | Slave           | 200 OK         | true
                                       | Unknown         | 404 Not Found  | UNKNOWN
  |========================================================================================
  
  
  