`wp_http_supports()` doesn't reflect what Requests can do

[dd32]

While reviewing what parts of WP_HTTP can be removed in #37705, I noticed that wp_http_supports() still performs it's checks against the WP_HTTP transports rather than querying against Requests to see if the request can be performed or not.

The only capability which we supported was ssl.

Three options:

1. Query SSL ability against Requests (if it supports that)
2. Deprecate and always return true;
3. Implement a small check to see if SSL requests will be able to proceed, checking for cURL features or openssl being available (and all the other streams requirements being satisfied).

The above options are in my order of preferences, we should support it if possible, but I'm not afraid of just no-oping the function.

Marking for 4.7, with the potential for 4.6.x backporting.

[jorbin]

I like the first option, though a quick look through Requests makes me think it doesn't have that functionality. @rmccue - Does that sound correct?

[dd32]

I couldn't see anything in Requests that we could use, but I also feel that adding a method for checking to see if we can *maybe* support SSL wouldn't be out of the question..

[desrosj]

@rmccue do you have any suggestions here?

[dd32]

Opened ​https://github.com/rmccue/Requests/issues/250 upstream.

[dd32]

Punting, it was broken in 4.6, mostly works still as long as the majority of the WP_HTTP logic remains in sync with Requests (which it is at present).

[desrosj]

I’m going to close this out as reported upstream. When Requests is updated and the PR above is merged, this will make its way in.

[jrf]

Requests 2.0.0 has been released and includes the change needed to address this.

The update to Requests 2.0.0 is expected to still go into WP 5.9. Once the upgrade patch has been merged, we should be able to address this ticket with relative ease.

Related: #54504

[peterwilsoncc]

Per discussion in a recent bug scrub, I am moving this off the 6.0 milestone as it depends on Requests 2.0.0 being merged.

Props @costdev, @chaion07.