search

feedbin / support

83 stars 11 forks source link

Should the ‘fetcher’ follow HTML redirects? #22

Open Zegnat opened 11 years ago

Zegnat commented 11 years ago

As I previously stated, some feeds do not import correctly. One such feed for me was http://cssquirrel.com/feed/. Google Reader uses this URL and loads the latest posts without a hitch.

Apparently when Google follows a link and receives an HTML document instead of a feed it will follow HTML redirects such as used by http://cssquirrel.com/feed/:

    <meta http-equiv="Refresh" content="0; URL=http://www.cssquirrel.com/blog/feed/">

Feedbin does not handle this and so the feed import failed. Should Feedbin be made to try HTML responses for HTML redirects as well or is the stricter handling of Feedbin better? This should not be an issue during normal use but with all these people slinging their OPML files around…

benubois commented 11 years ago

Feedbin should follow all server generated redirects with a 2xx or 3xx status code and a location header. Meta refresh is not followed at this time, but it might be an option.

On Mar 26, 2013, at 6:15 AM, Martijn van der Ven notifications@github.com wrote:

As I previously stated, some feeds do not import correctly. One such feed for me was http://cssquirrel.com/feed/. Google Reader uses this URL and loads the latest posts without a hitch.

Apparently when Google follows a link and receives an HTML document instead of a feed it will follow HTML redirects such as used by http://cssquirrel.com/feed/:

<meta http-equiv="Refresh" content="0; URL=http://www.cssquirrel.com/blog/feed/">

Feedbin does not handle this and so the feed import failed. Should Feedbin be made to try HTML responses for HTML redirects as well or is the stricter handling of Feedbin better? This should not be an issue during normal use but with all these people slinging their OPML files around…

— Reply to this email directly or view it on GitHub.