Re: OneConnect, HTTP pipelining and security

The RFC:

   A client that supports persistent connections MAY "pipeline" its
   requests (i.e., send multiple requests without waiting for each
   response). A server MUST send its responses to those requests in the
   same order that the requests were received.

In case you apply OneConnect it would be required to avoid connection pooling for pipelined requests. Otherwise there would be no way to demultiplex the server replies as there is no concept of message identifier in the http protocol, afaik.