ServiceWorker making same-origin requests via fetch won't include credentials (Legacy Chrome version)












0















I'm using the library sw-precache to generate a service worker script which precaches some resources on a web application. Everything is working well on modern Chrome versions.



That said -- I am also supporting Chrome 53 for legacy users, I'm seeing same-origin requests which don't include credentials (cookies, basic http auth, etc..) despite the generated service worker setting credentials: 'same-origin' or credentials: 'include' for the calls to fetch.



Also the initial request for the service worker script itself doesn't include credentials.



This is the relevant section of the script generated by sw-precache:



  var request = new Request(cacheKey, {credentials: 'include'});
return fetch(request).then(function(response) {


In Chrome 70 (latest), the same script results in requests which includes credentials. I looked through the Chrome release notes and didn't find anything related to this. So I'm wondering when this changed and what version of Chrome I would need to recommend my users upgrade to for the fix. Also wondering if there are any ideas for workarounds for these legacy Chrome users.



Screenshot of the request headers in Chrome 56










share|improve this question





























    0















    I'm using the library sw-precache to generate a service worker script which precaches some resources on a web application. Everything is working well on modern Chrome versions.



    That said -- I am also supporting Chrome 53 for legacy users, I'm seeing same-origin requests which don't include credentials (cookies, basic http auth, etc..) despite the generated service worker setting credentials: 'same-origin' or credentials: 'include' for the calls to fetch.



    Also the initial request for the service worker script itself doesn't include credentials.



    This is the relevant section of the script generated by sw-precache:



      var request = new Request(cacheKey, {credentials: 'include'});
    return fetch(request).then(function(response) {


    In Chrome 70 (latest), the same script results in requests which includes credentials. I looked through the Chrome release notes and didn't find anything related to this. So I'm wondering when this changed and what version of Chrome I would need to recommend my users upgrade to for the fix. Also wondering if there are any ideas for workarounds for these legacy Chrome users.



    Screenshot of the request headers in Chrome 56










    share|improve this question



























      0












      0








      0








      I'm using the library sw-precache to generate a service worker script which precaches some resources on a web application. Everything is working well on modern Chrome versions.



      That said -- I am also supporting Chrome 53 for legacy users, I'm seeing same-origin requests which don't include credentials (cookies, basic http auth, etc..) despite the generated service worker setting credentials: 'same-origin' or credentials: 'include' for the calls to fetch.



      Also the initial request for the service worker script itself doesn't include credentials.



      This is the relevant section of the script generated by sw-precache:



        var request = new Request(cacheKey, {credentials: 'include'});
      return fetch(request).then(function(response) {


      In Chrome 70 (latest), the same script results in requests which includes credentials. I looked through the Chrome release notes and didn't find anything related to this. So I'm wondering when this changed and what version of Chrome I would need to recommend my users upgrade to for the fix. Also wondering if there are any ideas for workarounds for these legacy Chrome users.



      Screenshot of the request headers in Chrome 56










      share|improve this question
















      I'm using the library sw-precache to generate a service worker script which precaches some resources on a web application. Everything is working well on modern Chrome versions.



      That said -- I am also supporting Chrome 53 for legacy users, I'm seeing same-origin requests which don't include credentials (cookies, basic http auth, etc..) despite the generated service worker setting credentials: 'same-origin' or credentials: 'include' for the calls to fetch.



      Also the initial request for the service worker script itself doesn't include credentials.



      This is the relevant section of the script generated by sw-precache:



        var request = new Request(cacheKey, {credentials: 'include'});
      return fetch(request).then(function(response) {


      In Chrome 70 (latest), the same script results in requests which includes credentials. I looked through the Chrome release notes and didn't find anything related to this. So I'm wondering when this changed and what version of Chrome I would need to recommend my users upgrade to for the fix. Also wondering if there are any ideas for workarounds for these legacy Chrome users.



      Screenshot of the request headers in Chrome 56







      service-worker sw-precache






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 29 '18 at 17:56







      Kenn

















      asked Dec 29 '18 at 16:15









      KennKenn

      1,38212136




      1,38212136
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53971197%2fserviceworker-making-same-origin-requests-via-fetch-wont-include-credentials-l%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53971197%2fserviceworker-making-same-origin-requests-via-fetch-wont-include-credentials-l%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Monofisismo

          Angular Downloading a file using contenturl with Basic Authentication

          Olmecas