How Can I Edit Google Chrome's 'History Provider Cache' File?

2

1

I'm interested in editing (not completely deleting) contents of some of Google Chrome's cache files. In particular, the 'History Provider Cache' (found in ~/Library/Application Support/Google/Chrome/Default on Mac). As this other question suggests, it appears to simply be a SQLite file. Unfortunately, when I try to open it using a SQLite browser (MesaSQLite) I'm asked for an encryption key.

So, I'd welcome any suggestions on how to either (1) determine the encryption key, or (2) an alternate way to edit this file.

The end goal is to be able to remove specific annoying suggestions in the Omnibar. I've read countless other techniques, but none seem to remove suggestions that have the clock icon next to it. Some say deleting this file entirely will do the trick (and I imagine it will), but I don't wish to trash my entire browsing history. I find most of the suggestions to be useful and helpful, and I'd like to preserve that.

dissolved

Posted 2012-02-18T18:36:45.277

Reputation: 181

Do the "other techniques" include simply deleting selected items from the History page (chrome://history/) ? – William Jackson – 2012-02-18T20:53:45.467

Take a look at chrome://about/ in the address/Search bar fo Google Chrome...

This entry may be what's you're looking for: chrome://net-internals/#httpCache

Click on Explore cache entries link – climenole – 2012-02-18T21:07:00.433

@WilliamJackson - Yes, but deleting from the history doesn't remove them from the cache. – dissolved – 2012-02-19T22:23:32.193

@climenole - Unfortunately, best I can tell, that only allows me to browse the cache, not edit it. Did I miss something? – dissolved – 2012-02-19T22:32:33.867

Answers

2

Note the answer to the other question is wrong when it asserts that all Chrome data files are SQLite3. History Provider Cache uses Google's Protocol Buffers format. To edit a file using the Protocol Buffers format, try Google's own protobufeditor. However, you'll probably need to write a proto definition for it to work.

An SQLite3 client can't distinguish non-SQLite3 data from encrypted data, which is why you're prompted for a key. It doesn't actually mean you're dealing with an encrypted database (the command line client makes this clear, printing the message "Error: file is encrypted or is not a database" when it doesn't recognize the format of a file).

References:

outis

Posted 2012-02-18T18:36:45.277

Reputation: 388

Asked: 2012-02-18T18:36:45.277

Viewed: 7 981 times

Active: 2012-12-03T04:02:50.863