Update feed on 301 redirects, 410 gone

[anonymous]

If a request for a feed returns an HTTP 301 Moved Permanently status the location for the feed should be updated in the database. If a 404 Not Found or a 410 Gone is received, the feed should be deprecated.

It might be desirable to defer each of these operations until a couple of similar responses have been received, to avoid having temporary configuration glitches throw off the feed configuration permanently.

[mbonetti]

Good point. Deferring these actions could prove tricky, though, as we don't store the feed's status across updates.

[ebyryan]

I think the 301 permanent move would be safe to implement. The 404 could be temporary though. Perhaps they could be either flagged or added to a "dead" category? Then users could view the category or their list for the flag to see what items need action.

[ebyryan]

Another option for 404's and the like would be to bring up a page after the update with a list of the problem feeds and allow actions to be done such as delete, update url, etc before going back to frontpage.

[mbonetti]

If anyone could provide an URL of a feed that throwing a 301, that could help testing

[sdcosta]

THere are lots of test cases with return codes over here http://diveintomark.org/tests/client/http/