[wp-trac] [WordPress Trac] #24646: fetch_feed() returns WP_Error with "A valid URL was not provided"

[WordPress Trac]

#24646: fetch_feed() returns WP_Error with "A valid URL was not provided"
--------------------------+--------------------
 Reporter:  husdaman      |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  3.5.3
Component:  Feeds         |     Version:  3.5.2
 Severity:  major         |  Resolution:
 Keywords:                |
--------------------------+--------------------

Comment (by mboynes):

 Replying to [comment:21 nacin]:

 > Which port? What kind of request? What protocol? What are you trying to
 accomplish? What's your site's port? How are you making this query?

 I'm querying an elasticsearch server on port 9200. I'm also accessing it
 through a local IP, as it so happens.

 > You said latest nightly build. Just to be clear — are you having issues
 on 3.5.2, or only trunk?

 Sorry for the confusion; I'm experiencing this on trunk. I didn't realize
 that what went live in 3.5.2 and what's in trunk were different. I saw the
 commit was merged into 3.5.2 and didn't dig any further. I didn't test any
 of this on 3.5.2.

 > The changes to the HTTP API are not enumerated in the announcement post,
 no, but it is part of the first bullet point. There will be a post soon on
 API changes.

 Great, thanks. I think that's really important for developers.

 > No, that's what happened. WordPress 3.5.2 is, very simply, a security
 release for all previous WordPress versions.
 >
 > There was definitely the possibility that [24480] would break
 functionality. Believe it or not, we decided to break far less than we
 intended.
 >
 > Good thing is, 3.6 is just around the corner. We're happy to entertain
 any detailed information that can help improve wp_http_validate_url().

 I'd like to read more about the decision to limit the HTTP API. I couldn't
 find a ticket on the changes, so if you can point me in the right
 direction to follow the discussion, I'd really appreciate it. What I'd
 like to learn more about is, what's the rationale/threat? Why block local
 IPs? Why block non-standard ports? I'm clearly not evil enough, because I
 can't see the harm in either.

 Thanks!

--
Ticket URL: <http://core.trac.wordpress.org/ticket/24646#comment:23>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software