Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
service-worker: configure response status codes to treat as failed/offline with freshness strategy
See original GitHub issueWhich @angular/* package(s) are the source of the bug?
service-worker
Is this a regression?
No
Description
Expected behaviour: freshness strategy should return to user fetching requested data only if request was successful. If request is unsuccessful (has 500, 504 and other codes) it should return cached result instead of bad result. And bad result should not be cached at all.
But in reality:
freshness strategy return for user bad results.
Interestingly, freshness strategy works as expected if web-server absolutely died (network error: connection refused). I mean, all configured in dataGroup requests begin to return from cache and web-application works despite dead backend. It is different with particular bad request (as I described above).
Performance strategy works as expected (it returns cached results firstly)
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 11.2.19
Node: 14.8.2
OS: darwin x64
Angular: 11.2.14
Anything else?
Issue Analytics
- State:
- Created a year ago
- Reactions:36
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@gkalpak Seems like we have 20+ upvotes.
Could you move the request to your consideration list?
Interesting 😃 Would anyone be interested in working on a pull request by any chance? 😁