[wp-trac] [WordPress Trac] #11613: HTTP API may make a request on an unsupporting transport

[WordPress Trac]

#11613: HTTP API may make a request on an unsupporting transport
--------------------------+-------------------------------------------------
 Reporter:  dd32          |       Owner:           
     Type:  defect (bug)  |      Status:  new      
 Priority:  normal        |   Milestone:  3.0      
Component:  HTTP          |     Version:  2.9      
 Severity:  normal        |    Keywords:  has-patch
--------------------------+-------------------------------------------------
 At present, When the HTTP API is called, It iterates through the
 transports testing each one to see if it can support the current request
 params (eg. SSL). This result is then stored for future requests.

 The issue i've run into, Is that i've added a case to a transport, that it
 should not be used if its a HEAD request (As it simply doesnt support it
 on that transport), The problem is, if a request is made before me, for
 say, a GET request, that transport gets cached for it, even if it doesnt
 support it..

 The attached patch adds a $key to the cache, which is a md5 of the
 serialized args.

 In most cases, this doesnt cause any issues, but if a host is using a
 lesser transport which cannot do everything (Such as FOpen) then errors
 can be hit that the transport doesnt support it.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/11613>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software