导致'ServiceWorkerGlobalScope'执行'fetch'失败的原因：'only-if-cached'只能设置'same-origin'模式错误？ [英] What causes a Failed to execute 'fetch' on 'ServiceWorkerGlobalScope': 'only-if-cached' can be set only with 'same-origin' mode error?

问题描述

升级到Chrome 64后，我意识到当我在新标签页上加载页面时会出现此错误。

。希望它能尽快解决，或者有关该问题的更多信息将会公布。

Paul Irish实施了一项临时工作，具体如下：

  if（e.request.cache ==='only-if-cached'&& e.request.mode！=='相同-origin'）{
 return; 
} 
  

我在服务工作者的回调中运行它安装和获取侦听器并防止出错。

你可以看到< a href =https://github.com/paulirish/caltrainschedule.io/pull/51/commits/82d03d9c4468681421321db571d978d6adea45a7\"rel =noreferrer>完全提交保罗的代码。

After upgrading to Chrome 64, I realized that this error appears when I load my page on a new tab.

I can't identify where it is on the service worker. Here is my code to run the fetch:

self.addEventListener('fetch', function(event) {
   if (event.request.url.startsWith(self.location.origin)) {
       event.respondWith(
           caches.match(event.request).then(function(response) {
              return response || fetch(event.request).then(function(fetch_resp){
                  return fetch_resp;
              });
           })
       );
   }
});

Could anyone here, who has more knowledge about service worker, help me to solve this error?

解决方案

I believe this is a Chromium bug that has been reported here. Hopefully it will be fixed soon or some more information about the issue will be published.

Paul Irish implemented a temporary work around, which is as follows:

if (e.request.cache === 'only-if-cached' && e.request.mode !== 'same-origin') {
  return;
}

I ran it inside the callback for the service worker install and fetch listeners and it prevented the error.

You can see the full commit of Paul's code here.

这篇关于导致'ServiceWorkerGlobalScope'执行'fetch'失败的原因：'only-if-cached'只能设置'same-origin'模式错误？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！