Ticket #185 (new enhancement)

Opened 3 years ago

Last modified 2 years ago

Update feed on 301 redirects, 410 gone

Reported by: anonymous Assigned to: mbonetti
Priority: normal Milestone: Gregarius 0.5.5
Component: BUGS Version: 2.0
Severity: normal Keywords: http magpierss
Cc:

Description

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.

Change History

09/26/05 07:02:17 changed by mbonetti

  • keywords set to http magpierss.
  • milestone set to Gregarius 0.5.2.

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

10/03/05 04:11:19 changed by 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.

10/04/05 06:00:09 changed by 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.

10/14/05 08:14:28 changed by mbonetti

  • milestone changed from Gregarius 0.5.2 to Gregarius 0.5.3.

02/04/06 11:24:21 changed by mbonetti

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

02/04/06 15:02:00 changed by sdcosta

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

05/28/06 13:39:13 changed by kkkkoaaa

  • version set to 2.0.