finalcut / wp-feedlist

Automatically exported from code.google.com/p/wp-feedlist
0 stars 0 forks source link

Some Feeds, even when valid, return to feedList empty #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. setup feedlist to load feeds from a variety of sources
2. load page
3.

What is the expected output? What do you see instead?
expect to see items displayed; but instead get error saying feed is empty.

examples of urls that causes this behaviour
http://www.reas.com/reas.xml
http://reddit.com/.rss

Original issue reported on code.google.com by bill.raw...@gmail.com on 8 Aug 2006 at 9:21

GoogleCodeExporter commented 9 years ago
It appears both of these feeds are returning a 500 error.  I have attempted to
contact the folks at reddit.com to see if they will work with me to resolve the 
issue.

Wordpress uses a modified Magpie RSS reader class which uses the <a
href="http://sourceforge.net/projects/snoopy/">Snoopy HTTP Agent Class</a>

Doing a dump of the Snoopy HTTP "GET" request shows the 500 error message.  To 
be
honest though I'm not sure Snoopy is doing a "GET" and not a "POST".

Original comment by bill.raw...@gmail.com on 8 Aug 2006 at 10:12

GoogleCodeExporter commented 9 years ago
the problem seems to lie in the fact that wordpress uses Magpie, which in turn 
uses
Snoopy, which uses curl.  curl can't handle the way these servers respond to the
requests.

The parser, lastRSS (which, ironically, I was using pre wordpress 2), has no 
problems
with these urls and it uses fopen

Sadly, I believe there are some webhosts that don't allow the use of fopen and 
thus
the use of curl is required.  what a pain.

so I have three options:
1. redevelop feedList using lastRSS again.  Then users who can't use fopen are
screwed at all sites.
2. hack the wordpress source (not a very good idea).
3. leave as is and then users of curl are screwed at some sites
4. redevelop feedList using lastRSS and make a modified version of lastRSS 
which can
fall back to using wordpress's "snoopy" and thus "curl" implemention if fopen is
unavailable.

Original comment by bill.raw...@gmail.com on 8 Aug 2006 at 10:42

GoogleCodeExporter commented 9 years ago
well fopen is turned off because it actually is a security risk - but only if 
you
have evaluated paths being passed to fopen;  I'm not really sure what to do 
here.

Original comment by bill.raw...@gmail.com on 8 Aug 2006 at 10:52

GoogleCodeExporter commented 9 years ago
changed to low priorty becuase I'd rather spend the time making feedList fully 
stable
with magpie before I branch out into supporting multiple feed parsers.

Original comment by bill.raw...@gmail.com on 5 Oct 2006 at 7:45

GoogleCodeExporter commented 9 years ago
good news - this one is resolved thanks to an updated class-snoopy.php.  The 
problem
was that these sites actually sent the feed in gzip format and snoopy couldn't 
handle
it.  Now, with the snoopy included with feedlist - it can!

Original comment by bill.raw...@gmail.com on 29 Nov 2006 at 3:00