Feeds deactivated because error "not modified"

[a3rosol]

This happens way to often. A lot of my feeds get deactivated regularly because of this "error". But is this an error though? Technically, 302 is not an error code

[passiomatic]

I see it too. I believe it's not the "not modified" (which indeed is not an error) to increase the error count and thus causing the feed to be disabled, but the last HTTP error returned by the server which is not recorded correctly by the fetcher.

Actually the fetcher here is trying to be too clever, which makes the code hard to reason about. I need to simplify the whole process.

A workaround

As a temporary measure you may want to set to 0 the config max_errors setting, which makes Coldsweat to ignore the fetching errors.

[passiomatic]

This has been fixed in 0.9.8. You can update to the new release right now.