Repository navigation
Service Worker: Freshness strategy doesn't work #19489
Description
I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior
Service worker fetches and caches the response, but returns failed one to the client
Expected behavior
To fetch and return a response to the client + to cache it for offline usage
Minimal reproduction of the problem with instructions
https://ngsw.surge.sh/
Click "Load my timeline" - it uses "Freshness" strategy - there will be network error
Click "Load favorites" - it uses "Performance" strategy - works as intended
Source: https://github.com/webmaxru/pwatter/tree/ngsw
CC: @alxhub
What is the motivation / use case for changing the behavior?
Fix the bug
Environment
Angular version: 5.0.0.rc.0
Browser:
- [x] Chrome (desktop) version 61
Reacted by Marc Bornträger and Ivan Camilo Vásquez
Activity
ivancamilov commentedon Oct 23, 2017
I think this was resolved in 396c241, can you confirm, @alxhub?
webmaxru commentedon Oct 26, 2017
Fixed by #19764
angular-automatic-lock-bot commentedon Sep 12, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.