| commit | fd30799f6f8a7d1366d97693b72b0b20be94d5c0 | [log] [tgz] |
|---|---|---|
| author | hubbe <hubbe@chromium.org> | Fri Sep 16 20:10:01 2016 |
| committer | Commit bot <commit-bot@chromium.org> | Fri Sep 16 20:13:24 2016 |
| tree | e2896b28bc40d0f0f00e56738e24561769a81dd7 | |
| parent | 343264820eb254bdab3dbeef0082e8e1bb307532 [diff] |
Store, use and send etags. We use them to validate/invalide cached but expired data. We send Match-If headers to prevent mixing of old/new cached data. This should all be safe to do, since the HTTP cache already sends etags to manage it's internal cached state, this CL just extends this behavior to apply to client-side in-memory cached data as well. BUG=504194 Review-Url: https://codereview.chromium.org/2338963002 Cr-Commit-Position: refs/heads/master@{#419264}