[wp-trac] [WordPress Trac] #25738: WP_HTTP uses transports that incorrectly claim to support a request

[WordPress Trac]

#25738: WP_HTTP uses transports that incorrectly claim to support a request
--------------------------+------------------
 Reporter:  dd32          |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  3.8
Component:  HTTP          |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+------------------

Comment (by dd32):

 > cURL has a fairly large install base, and the advantage of handling more
 in C gives us better performance. Adding parallel request support would
 help with this, but I don't think anyone has proposed that yet.

 I'm yet to see any significant advantage in performance using cURL, doing
 unscientific testing (and excluding any times which were crazy-far from
 the rest) showed curl and streams generally within 10ms of each other (on
 a 400ms request) on small files, and within 200ms on downloading WordPress
 (~5s). When I tried on a slower connection (ironically, my VPS) cURL was
 averaging 33s, while Streams averaged 29s.

 What I'm saying.. is any significant performance gains between the two are
 almost irrelevant for WordPress, if we were making thousands of requests
 per hour then squeezing 10ms out here and there makes a huge difference,
 but in this case it's more likely remote severs are the performance
 bottleneck.

 > I'm not sure special-casing it is a good idea; more options = worse.
 In general I agree, however, this is a scenario where we need the most
 compatibility possible, if HTTPS via cURL fails, we need to try HTTPS via
 Streams before falling back to HTTP.
 We also don't want to prevent a site from getting update notifications,
 which is why we have to have a HTTP fallback.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/25738#comment:13>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software