ServiceWorker returns "503 OK (from ServiceWorker)" on accessing dynamic content while offline (Chrome)

[cars10]

Hi, using beta16 i cannot access cached dynamic content. Chrome shows a "503 OK (from ServiceWorker)" and no content is loaded, even though its listed in the caches in chrome. beta11 works fine.

Edit:
Initially i only tested chrome (59), its broken there. Firefox (54) works as expected and loads the content correctly.

[avatsaev]

same problem here,

Tested in Firefox, everything seems to be working fine. Chrome related issue?

[BorntraegerMarc]

With beta 14 it worked fine for me

[webmaxru]

I believe it's connected with 6f930b8

[lacolaco]

As far as I can see, external dynamic contents won't cached with beta-16 (including 6f930b8).

BTW, Stephen's blog article says as following:

by creating a dynamic cache group, matching files that are fetched by the Service Worker will also be cached.

but the firebase dynamic group doesn't seem working correctly.

Actually, the contents is not available in offline

cc/ @StephenFluin

[cars10]

Any update on this?

[THLAP]

I am also having issues around caching dynamic content on beta16. I am not sure if they are exactly the same as yours. See my explanation in #179.

As a side note the "performance" strategy was working for me, the only caveat being dynamic content is only cached on the second page load due to async nature of the service worker. My api calls are completing before the service worker is controlling the page. This is fine for me but at first I was expecting to load the page once and take it offline and everything work, which it didn't.

[St1c]

same issue here, I'm trying to implement google maps via angular google maps library, and I'm getting 503 for async loading of the library