This is more broadly part of a cleanup/eraser effort for reducing about pages.

Worth noting that chrome://view-http-cache was handy in looking into the corruption issue facebook reported...

Also, net-internals currently has a link to chrome://view-http-cache, so if we remove it, need to update net-internals as well.  It doesn't link to individual entries, so just need to remove one small piece of an HTML file.

Seems reasonable, but I do use it occasionally for debugging myself as well. Hmm.

I used it 2 days ago and it was valuable at the time. Of course, chrome developers can use cachetool instead, but if the cache page doesn't require much logic I'd like to keep it (and upgrade it).

Sounds like we should take them off the chopping block then? Feel free to close this bug if you think so.

I'd much prefer that we keep it if it's not a maintenance burden. Tentatively closing.