--cache-exclude-status still uses existing cache entries that are excluded (original) (raw)

I think this might not be what people expect. Let's say you are using a cache, for example in CI, and you are adding the --cache-exclude-status flag at some point, for example ignoring status 418. If there are already cache entries for that, they will still be used and pages that previously returned 418 aren't checked again. I think this is counter intuitive and annoying in some cases. You'll either have to clean these cache entries manually or throw away the whole cache.

Instead, lychee could ignore existing cache entries with status that is excluded by --cache-exclude-status.