Chromium and Chrome Dev Channel has (off by default) pipelining. Pipelining can only be done for idempotent requests, (ie GET only), has head of line blocking

Chromium and Chrome Dev Channel has (off by default) pipelining. Pipelining can only be done for idempotent requests, (ie GET only), has head of line blocking problems, and can break proxies. Also, its very difficult to handle errors in a pipelined situation. For example, if the 2nd request in a pipeline fails, but the server has been processing 3rd and 4th concurrently, what response does it give? I think most engineers would agree that multiplexing over a single connection is better and less error-prone than pipelining.