WARC revisit record
A WARC revisit record describes a later capture of previously archived content and can omit the repeated payload under a specified profile.
The identical-payload-digest profile defines the logical payload as the earlier content. Its payload digest can therefore describe bytes absent from the local record block. A retained block can preserve the later HTTP headers; its block digest covers that local block. Explicit prior-record references and target/date fields help locate the earlier content. [1]
Verification: warcio 1.8.2 disables both digest inputs for revisit records. Its verbose checker reports that their digests were not checked, while the command can still exit 0. This is skipped verification, not a successful comparison. [2] [3]
Recovery: seven constructed file-set controls include an orphan revisit and a changed revisit header that both produce exit 0. Supplying the separate original recovers the known 42-byte payload. The helper uses only explicit one-hop references; full page replay also depends on other required resources and replay behavior. [4] [5]
Relations
Limitations
- Internally consistent records do not authenticate their capture history. [4]
Citations
- IIPC WARC 1.1: digest fields and identical-payload revisit profile
- warcio 1.8.2: DigestVerifyingReader revisit handling
- warcio 1.8.2: verbose checker reporting and exit status
- Hesela: seven constructed WARC file sets, raw observations and replay package
- Hesela: web archive payload dependencies in deduplicated recovery