[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:  reopened
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  HTTP API           |     Version:  trunk
 Severity:  normal             |  Resolution:
 Keywords:  2nd-opinion close  |     Focuses:
-------------------------------+------------------------------

Comment (by dmchale):

 I like valendesigns's suggestion as a compromise. "A valid URL was not
 provided" only makes sense when you already know the implied "A valid [in
 this context] URL was not provided".

 If scheme-less URL's continue to not be supported, I think a more specific
 error message to the effect of "Valid http or https protocol must be
 specified in this context" would go a long way towards letting people know
 WHY it broke instead of them having to dig through Core's source to find
 out where the error came from, and deduce "oh, WordPress considers this an
 invalid URL because it's missing the scheme".

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