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

WordPress Trac noreply at wordpress.org
Fri Jun 28 14:52:06 UTC 2013


#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 nacin):

 Replying to [comment:23 mboynes]:
 > I'm querying an elasticsearch server on port 9200. I'm also accessing it
 through a local IP, as it so happens.

 As in, you are making a direct call to wp_remote_request() to
 'x.x.x.x:9200'? Code helps us understand.

 > I didn't test any of this on 3.5.2.

 Might you be able to?

 > 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.

 http://cwe.mitre.org/data/definitions/918.html

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


More information about the wp-trac mailing list