WordPress.org

Make WordPress Core

Opened 8 years ago

Closed 6 years ago

#27008 closed defect (bug) (wontfix)

dashboard feed error when behind proxy (RSS Error: WP HTTP Error: 111)

Reported by: richardrigby Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.8.1
Component: Feeds Keywords: needs-patch
Focuses: Cc:

Description

using a new install of wordpress 3.8.1, on a web server which is behind a proxy.

proxy settings all work well for installing themes, plugins, etc., but the feeds on the dashboard don't seem to honour the proxy settings - errors are shown:

RSS Error: WP HTTP Error: 111: Connection refused

is there anywhere else that the proxy settings should be configured for the rss feeds?

Change History (5)

#1 @SergeyBiryukov
8 years ago

  • Component changed from General to Feeds

#2 follow-up: @dd32
8 years ago

FWIW, Feeds & Plugin installations use the same proxy configurations.

Are these with WordPress.org default feeds, or a custom URL?
Is there a chance that the RSS error is cached from before you defined the proxy settings?

#3 in reply to: ↑ 2 @richardrigby
8 years ago

Replying to dd32:

FWIW, Feeds & Plugin installations use the same proxy configurations.

Are these with WordPress.org default feeds, or a custom URL?
Is there a chance that the RSS error is cached from before you defined the proxy settings?

thanks for your reply.

even when completely clearing all caches/opening a different browser on a different machine, the same error is displayed.

this is with the default feeds 'wordpress news' etc.

as mentioned, the proxy settings work just fine for plugins, themes, etc.

if i point the wordpress install at a proxy which i can monitor, i can see requests going through when searching plugins/themes, but nothing for rss feeds.

if it makes any difference, this is a multi site set up, with files in a sub directory.

everything else is working fine, so not a major issue.

if i can find some time, i'll see if can dig around a bit more, and spot any clues as to why this is happening.

thanks again for your help,

richard

#4 @dd32
8 years ago

How odd.

The cache I was referring to wasn't browser or computer specific however, rather it's a Transient which has a default timeout of 12hours.

A starting point for debugging is https://core.trac.wordpress.org/browser/trunk/src/wp-includes/class-feed.php#L18
I'd disable the cacheing in WP_Feed_Cache_Transient (make load() return false), and then test again, then look into WP_SimplePie_File which uses the same HTTP fetching commands as Plugin installs.

Good luck and I'll be interested in hearing what you find

#5 @chriscct7
6 years ago

  • Keywords needs-patch added
  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Closing as wontfix. Complete lack of interest on the ticket over the last 2 years. Feel free to reopen when more interest re-emerges (particularly if there's a patch)

Note: See TracTickets for help on using tickets.