New issue
Advanced search Search tips

Issue 732344 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Chrome service worker not intercepting cached requests

Reported by erik.w...@baqend.com, Jun 12 2017

Issue description

Chrome Version       : 60.0.3112.24
URLs (https://service-worker-test.app.baqend.com/) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: no service worker
    Firefox: OK 53.0.3
         IE: no service worker

What steps will reproduce the problem?
See https://stackoverflow.com/questions/44421110/chrome-service-worker-not-intercepting-cached-requests

What is the expected result?
Every request should go through the fetch method of the service worker whether these resources are in the browser cache or not.

What happens instead?
With enabled browser cached, only uncached or revalidated resource requests go through the service worker.
 
Components: Platform>DevTools>Network
Labels: -Type-Bug -Pri-3 hasbisect-per-revision M-61 OS-Linux OS-Mac OS-Windows Pri-1 Type-Bug-Regression
Owner: allada@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Windows 10, Ubuntu 14.04 and Mac 10.12.5 using reported version #60.0.3112.24 and latest canary #61.0.3130.0.

Bisect Information:
=====================
Good build: 55.0.2855.0	 Revision(417475)
Bad Build : 55.0.2856.0	 Revision(417772)

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/41832e5474cea7ddeafefac5872134408fdfefdc..ce98e6c4a756a41f57ff444a40267a66f52e91e8

From the above change log suspecting below change
Review URL: https://codereview.chromium.org/2274233002

allada@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks...!!
Owner: caseq@chromium.org
I'm not sure that this is actually a bug. I think it is just the in-memory cache in Chrome's rendering engine Blink that serves the image requests so they don't even reach the Service Worker.
Owner: jarhar@chromium.org

Sign in to add a comment