Feature #5461

Add pipelining to Net::HTTP

Added by Eric Hodel almost 4 years ago. Updated almost 3 years ago.

Assignee:Yui NARUSE


The attached patch adds HTTP/1.1 pipelining support to Net::HTTP.

Pipelining is only performed on HTTP/1.1 servers. Net::HTTP will check if the server supports pipelining by using the first request in the list. The user can override this via setting (({http.pipelining = true})).

If a server does not support pipelining or there is an error during pipelining an error will be raised that contains the requests that not have been delivered yet and the responses that have been received.

The patch includes documentation explaining the fine details.


requests = []
requests << Net::HTTP::Get.new('/images/bug.png')
requests << Net::HTTP::Get.new('/images/date.png')
requests << Net::HTTP::Get.new('/images/find.png')

http = Net::HTTP.new 'localhost'
http.start do
http.pipeline requests do |req, res|
open File.basename(req.path), 'wb' do |io|
io.write res.body

Implementation notes:

  • The current Net::HTTP tests make it very difficult to test bad behavior by servers. In test/net/http/utils.rb I introduced a method to replace Net::BufferedIO with a subclass that can behave incorrectly.
  • Net::HTTP#pipeline does not fall back to sending requests one-by-one for HTTP/1.1 servers. I think this is acceptable as the user can use existing Net::HTTP code to send requests one-by-one.


net.http.rb.pipeline.patch Magnifier (26.2 KB) Eric Hodel, 10/19/2011 07:37 AM

Related issues

Related to Ruby trunk - Feature #5064: HTTP user-agent class Assigned 07/21/2011


#1 Updated by Yusuke Endoh over 3 years ago

  • Status changed from Open to Assigned
  • Assignee set to Yui NARUSE

I tentatively assign this issue to Naruse-san because
he is running for the maintainer of net/http.

Yusuke Endoh mame@tsg.ne.jp

#2 Updated by Yusuke Endoh almost 3 years ago

  • Target version changed from 2.0.0 to next minor

Also available in: Atom PDF