Connection management broken in the proxy case
Submitted by Christophe Gillette
Assigned to libsoup-maint@gnome.bugs
Link to original bug (#591386)
Description
From the todo list: "Proxy connection management is currently broken; each origin server gets its own set of connections to the proxy. They should all share the same connections"
From mailing list: http://mail.gnome.org/archives/libsoup-list/2009-July/msg00002.html
It would be nice to be able to specify the maximum number of connections when connecting to a proxy independently from the current max-conn-per-host value, and have libsoup reuse the connections to the proxy and not close them/cache them based on the origin server.
As a specific example, using webkit to load a rather large site (for ex: amazon.com: about 90 resources) with a max-conn-per-host set to 6 creates and closes 30 sockets (8 remaining open as it is the maximum number of connections across hosts). On high latency networks, this behavior significantly degrades webkit's performance.
Version: 2.27.x