Take these three example requests:
$ curl 10.111.95.102:8091/pools/default
|
$ http 10.111.95.102:8091/pools/default
|
cbq> select CURL("GET", "10.111.95.102:8091/pools/default");
|
which produce the following (respectively) in http_access.log:
10.111.95.1 - - [27/Jan/2017:21:40:27 +0000] "GET /pools/default HTTP/1.1" 200 3742 - curl/7.49.1
|
10.111.95.1 - - [27/Jan/2017:21:40:33 +0000] "GET /pools/default HTTP/1.1" 200 3742 - HTTPie/0.9.3
|
10.111.95.1 - - [27/Jan/2017:21:44:15 +0000] "GET /pools/default HTTP/1.1" 200 3757 - -
|
Obviously, this isn't dependant on the receiving end being CB, but it demonstrates the point. I suspect that we would want this from a best practice perspective anyway, but it's going to be vital for debugging issues where N1QL CURL is being aimed at a CB cluster.