[wp-trac] [WordPress Trac] #17251: Determine if any WP_HTTP transport can be used before making the request
WordPress Trac
wp-trac at lists.automattic.com
Wed Apr 27 13:07:58 UTC 2011
#17251: Determine if any WP_HTTP transport can be used before making the request
-------------------------+-----------------------
Reporter: mdawaffe | Owner: dd32
Type: enhancement | Status: assigned
Priority: normal | Milestone: 3.2
Component: HTTP | Version: 3.2
Severity: normal | Resolution:
Keywords: has-patch |
-------------------------+-----------------------
Comment (by sivel):
This is just a thought, but what if we added the functionality for a
fallback URL, or fallback protocol? If the request can not be completed
for the URL based on the tests, it can fallback to another URL or
protocol.
Not that I am not open to new ideas, but it has come up several times that
we should allow someone to be able to specify the transport they wanted to
use, but it was generally dismissed, as that is not what the HTTP API was
really meant for. I realize that this can already be done with filters,
and I am actually for this change, I just want to make sure that we aren't
just throwing out previous decisions without considering why they were
done previously.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/17251#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list