New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 700691 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Feature



Sign in to add a comment

Please support the Cache Directory Tagging Standard

Reported by mapr...@gmail.com, Mar 11 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36

Steps to reproduce the problem:
See http://www.brynosaurus.com/cachedir/spec.html
Adopting such "standard" would help a lot people doing full-system backups of their desktop hosts, where browser cache might have a relevant size and definitely doesn't need backup.

What is the expected behavior?
a CACHEDIR.TAG file (with the appropriate content) to be present in ~/.cache/chromium/ and ~/.config/chromium/Default/Application Cache/, and all other relevant cache directories.

What went wrong?
.

Did this work before? N/A 

Chrome version: 56.0.2924.76  Channel: n/a
OS Version: 
Flash Version:
 

Comment 1 by mmenke@chromium.org, Mar 14 2017

Components: Internals>Network>Cache
Labels: -Pri-2 Pri-3

Comment 2 by hdodda@chromium.org, Oct 16 2017

Cc: hdodda@chromium.org
Labels: M-63
Status: Untriaged (was: Unconfirmed)
This looks more like a feature request , hence marking it as untraiged for further inputs on this.

Thanks!

Sign in to add a comment