New issue
Advanced search Search tips

Issue 845629 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 747718
Owner: ----
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

"Time Cached" value of 1970-01-01 for constructed responses in DevTools

Project Member Reported by jeffy@chromium.org, May 22 2018

Issue description

Chrome Version       : 66.0.3359.181
OS Version: OS X 10.13.4
URLs (if applicable) : https://cdn.rawgit.com/jeffposnick/6b5c1137965ae37c914d1d7ca3ceba81/raw/da4b72dc907ef2c810d36c837f1a4c17a20be67b/index.html

What steps will reproduce the problem?
1. You can reproduce this by visiting the test page linked to above, or just calling 

    caches.open('my-cache')
      .then(c => c.put('/' + Date.now(), new Response('ignored'))); 

from any page.

What is the expected result?
When viewing the new cache entry in the DevTool's Application panel, the "Time Cached" column should be either empty, or ideally, set to the date corresponding to when cache.put() was called.

What happens instead of that?
The localized version epoch value of Jan 1, 1970 is used instead.

UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36
 
Screen Shot 2018-05-22 at 4.17.34 PM.png
101 KB View Download
Mergedinto: 747718
Status: Duplicate (was: Untriaged)

Sign in to add a comment