5 releases

0.2.3 Sep 2, 2024
0.1.3 May 21, 2024
0.1.2 May 21, 2024
0.1.1 May 17, 2024
0.1.0 May 14, 2024

#804 in Parser implementations

MIT/Apache

30KB
655 lines

ci A work-in-progress, safe, rust-based chrome cache parser.

It parses the cache entries themselves and exposes a reader interface for the cached data. You can use it to programmatically to inspect the cache index and, for example, display the known cache keys (e.g., URIs) stored in the cache, along with some entry metadata (timestamp, etc.). It only supports cache keys stored inline with the cache entry, not the longer, out-of-band cache keys.

It is very much so still a work-in-progress, though I am using it in a "real" application already. I hope to continually add features and improve the interfaces as time permits. Feel free to get in touch if you want to contribute.

Run The Example

By default, it'll display the cache entries from a typical google chrome cache path. Provide --path to point it somewhere else.

cargo run --example display-chrome-cache

Example Usage

use std::{path::PathBuf};

use chrome_cache_parser::{CCPError, CCPResult, ChromeCache};
use chrono::{DateTime, Local};

let cache = ChromeCache::from_path(PathBuf::from(path)).unwrap();

let entries = cache.entries().unwrap();

entries.for_each(|e| {
    let e = e.get().unwrap();
    println!("[{:?}\t=>\t{:?}]: {:?}", e.hash, e.key, DateTime::<Local>::from(e.creation_time));
});

Implementation

The implementation is mostly just transmutations via the zerocopy library and some lazy traversing of the cache index's hash table and internal entry linked lists.

Background

For an overview of the chrome cache implementation, see here.

The Chromium sources were helpful for understanding the cache format.

Particularly:

Dependencies

~1.9–2.7MB
~44K SLoC