Version: unspecified (using KDE 4.5.1) OS: Linux log from my webserver 85.180.145.226 - - [16/Sep/2010:18:24:58 +0200] "GET /lia/?feed=rss2 HTTP/1.1" 404 283 "-" "Akregator/1.6.5; syndication" 85.180.145.226 - - [16/Sep/2010:18:25:58 +0200] "GET /lia/?feed=rss2 HTTP/1.1" 404 283 "-" "Akregator/1.6.5; syndication" 85.180.145.226 - - [16/Sep/2010:18:26:58 +0200] "GET /lia/?feed=rss2 HTTP/1.1" 404 283 "-" "Akregator/1.6.5; syndication" 85.180.145.226 - - [16/Sep/2010:18:27:58 +0200] "GET /lia/?feed=rss2 HTTP/1.1" 404 283 "-" "Akregator/1.6.5; syndication" 85.180.145.226 - - [16/Sep/2010:18:28:58 +0200] "GET /lia/?feed=rss2 HTTP/1.1" 404 283 "-" "Akregator/1.6.5; syndication" 85.180.145.226 - - [16/Sep/2010:18:29:58 +0200] "GET /lia/?feed=rss2 HTTP/1.1" 404 283 "-" "Akregator/1.6.5; syndication" 85.180.145.226 - - [16/Sep/2010:18:30:58 +0200] "GET /lia/?feed=rss2 HTTP/1.1" 404 283 "-" "Akregator/1.6.5; syndication" 85.180.145.226 - - [16/Sep/2010:18:31:58 +0200] "GET /lia/?feed=rss2 HTTP/1.1" 404 283 "-" "Akregator/1.6.5; syndication" 85.180.145.226 - - [16/Sep/2010:18:32:58 +0200] "GET /lia/?feed=rss2 HTTP/1.1" 404 283 "-" "Akregator/1.6.5; syndication" 85.180.145.226 - - [16/Sep/2010:18:33:58 +0200] "GET /lia/?feed=rss2 HTTP/1.1" 404 283 "-" "Akregator/1.6.5; syndication" 85.180.145.226 - - [16/Sep/2010:18:34:58 +0200] "GET /lia/?feed=rss2 HTTP/1.1" 404 283 "-" "Akregator/1.6.5; syndication" 85.180.145.226 - - [16/Sep/2010:18:35:58 +0200] "GET /lia/?feed=rss2 HTTP/1.1" 404 283 "-" "Akregator/1.6.5; syndication" 85.180.145.226 - - [16/Sep/2010:18:36:58 +0200] "GET /lia/?feed=rss2 HTTP/1.1" 404 283 "-" "Akregator/1.6.5; syndication" 85.180.145.226 - - [16/Sep/2010:18:37:58 +0200] "GET /lia/?feed=rss2 HTTP/1.1" 404 283 "-" "Akregator/1.6.5; syndication" Seriously Boys, what does a 404 tell some HTTP-Client? Right, it aint there. So why retrying every freaking minute for... just like... months? Please, in the name of Lee, if something 404s make the user re-enable the feed manually rather than trying aeons hitting an error which wont change because you hit the webserver stoicly. Reproducible: Always Steps to Reproduce: look at your webserver log Actual Results: it still did it :( Expected Results: IT SHOULD STOP, GODDAMIT! I wonder where the "annoying" severity is. Gah, ill leave it at normal, but you know why i might find it annoying. On a sidenote, this is the worst bugtracker i ever met. Seems Userfriendlyness isnt its plus-side.
You can configure the feed fetch interval (even for each feed separately).
(In reply to comment #1) > You can configure the feed fetch interval (even for each feed separately). Seriously? What HTTP Header do i need to send to set it?
*** This bug has been marked as a duplicate of bug 219372 ***
I don't think it will help with the akregator issue, but if the feed is permanently gone and won't be coming back, you should be returning 410, not 404.