[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):

 Looking at the chart above with the currently-known bugs, one might
 question why cURL is the first transport we try, it's three fold:
 * cURL was supposably going to have less bugs than our own PHP
 implementation.
  Over the years of WP_HTTP's lifespan we've replaced many functionalities
 of cURL with PHP code (redirects, some error handling, stream
 decompression/decoding) and more recently we've replaced the two PHP-
 implementations (fsockopen and fopen) with a new PHP Streams class (based
 on `stream_context_create()` ) in #25007
 * cURL is more memory efficient as most string operations happen in C,
 which supposably also makes cURL requests faster than Streams. This
 doesn't seem to hold true, as most requests complete in about the same
 time (+/- a %age point)
 * cURL had better SSL verification than Streams, which is no longer true
 as of #25007

 so when it comes down to it, it's mostly a legacy ordering, but there
 exists code out there which expects HTTP requests to be made via cURL and
 doesn't take into account its possible for it to use something else.

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