This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 595 - RFE: Option to cache results
Summary: RFE: Option to cache results
Status: NEW
Alias: None
Product: LinkChecker
Classification: Unclassified
Component: checklink (show other bugs)
Version: unspecified
Hardware: Other other
: P4 enhancement
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-11 23:39 UTC by Ricardo
Modified: 2013-11-03 07:35 UTC (History)
2 users (show)

See Also:


Attachments

Description Ricardo 2004-03-11 23:39:48 UTC
If you are managing a large number of links, it is important to understand the 
recent history of status codes returned from each URI. Temporary 404s, 403s, 
500s are quite common. So are DNS problems. The advice given by checklink 
to "Fix it Now" is sometimes wrong. It would be much better if the program 
could give advice like this: "This link has been consistently broken or 
unreliable for two weeks. Consider deleting it".

It would be great if checklink could write to and read from a status code 
cache -- but the ability to specify machine-readable output (so checklink users 
can manage their own cache) would be very helpful.