[wp-trac] [WordPress Trac] #37081: Requests: http_api_debug parameter no longer accurate

WordPress Trac noreply at wordpress.org
Mon Jun 13 01:34:55 UTC 2016


#37081: Requests: http_api_debug parameter no longer accurate
--------------------------+-----------------------
 Reporter:  johnbillion   |       Owner:  rmccue
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  4.6
Component:  HTTP API      |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+-----------------------
Changes (by rmccue):

 * owner:   => rmccue
 * status:  new => assigned


Comment:

 From WordPress' perspective, the transport is Requests, which is why I set
 it to that. (Also avoids bad plugins assuming that they can use a class
 based on the transport.) Requests exposes the transport it's using via
 [http://requests.ryanmccue.info/api/source-class-Requests.html#144-181
 Requests::get_transport()], unless it has been overridden in the options
 passed in.

 Right now, there's no way of getting the transport that was used for a
 request back out. We ''could'' save the options on the response object,
 but that seems like it could easily cause a memory leak.

 Any ideas how best to handle this?

--
Ticket URL: <https://core.trac.wordpress.org/ticket/37081#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list