When the feed encounters an error, the response should not be cached.
Essentially if the response status code is not between 200 and 300.
1. Access a feed, and have it cached.
2. Take the feed offline, e.g. returning a 503 or 404.
3. The feed/view is cached, but shouldn't be.
When the response is not successful, (ie. does not have a status code of >=200 and < 300), it should never be cached, it should instead show the previous response if cached, and the next request should reattempt to fetch the live feed.
Provide issue fork.
N/A
Active
2.0
Code
Repurposed this issue for something else as it's a duplicate of an existing issue.