Major Description
In forum posts as well as other tickets it has been discovered that the implicit pipelining netty/core-io uses doesn't work well with the go implementation of pipelining in http 1.1. In fact, it doesn't work at all and leads to all kinds of weird issues, especially prematurely aborted (n1ql) requests that return a status of "Closed' and 0 as the result count.
As a result, we need to disable pipelining for HTTP based services, but for performance reasons keep it for binary ops.