[wp-trac] [WordPress Trac] #30371: Allow for // rooted URLs in http request() calls (wp_remote_get(), etc)

[WordPress Trac]

#30371: Allow for // rooted URLs in http request() calls (wp_remote_get(), etc)
-------------------------+-----------------------------
 Reporter:  dmchale      |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  HTTP API     |    Version:  trunk
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 Calls to wp_remote_get() would fail with "A valid URL was not provided"
 because they did not start with an explicit scheme/protocol.

 However, this blocks references to url's which begin with `//`, which
 *are* valid URLs per RFC 1808 - http://www.ietf.org/rfc/rfc1808.txt

 If a developer requests a URL via a `//` reference, the assumption can be
 made that s/he knows the endpoint supports http AND https. If there are
 connection errors talking to a destination which does NOT support https,
 the developer should not be using the `//` reference in the first place.
 Argument that this is probably not something WordPress should try to
 decide for the developer.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/30371>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform