Reuse the existing cache when a server error occurs.

Created on 3 July 2025, 9 days ago

Problem/Motivation

When the feed encounters an error, the response should not be cached.

Essentially if the response status code is not between 200 and 300.

Steps to reproduce

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.

Proposed resolution

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.

Remaining tasks

Provide issue fork.

User interface changes

N/A

📌 Task
Status

Active

Version

2.0

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024