Cache Recovery

When a backend API temporarily fails, reqable can return a locally cached successful response so the page remains usable.

How it works

Send request → Receive response → Success? → Cache response → Return to page
                                   ↓ Error
                            Recovery enabled? → Find cache → Hit? → Return cached data
                                   ↓ No                 ↓ No
                              Return original error response

1. A processable successful response is stored in the browser's local cache.
2. For a temporary server failure such as 500, 502, 503, or 504, reqable looks up the request's cached response.
3. A cache hit replaces the failed response. A cache miss returns the original error.

Enable recovery

Open Settings → Cache recovery → Enable recovery.

WARNING

Cache recovery must be enabled from Settings. The switch in the Mock panel controls mocking only.

Cache policy

• Responses are persisted in IndexedDB and shared by pages with the same origin.
• Each domain has an independent entry limit, initially 1500.
• Once the limit is exceeded, the oldest entries are evicted in FIFO order.
• The precise cache key contains the request method, normalized URL, and request-body hash.
• If the precise key misses, reqable falls back to a key based on method, domain, and path.

Timestamp parameters configured in Settings are removed before cache-key calculation.

Applicable domains

Enter one type domain rule per line:

Type	Example	Meaning
regex	regex .*example\\.com.*	Regular-expression domain match.
fully	fully example.com	Exact domain match.
include	include localhost	Substring match.

Default rule:

regex (.*localhost.*|.*127.0.0.1.*)

Leave the rules empty to enable recovery on every page.

Settings

Option	Default	Description
Enable recovery	Off	Master switch.
Maximum entries per domain	1500	Range: 100–10000.
Applicable domain rules	localhost	Restricts where recovery is active.

Triggering status codes

Only the following server errors trigger recovery:

• 500 Internal Server Error.
• 502 Bad Gateway.
• 503 Service Unavailable.
• 504 Gateway Timeout.
• 520–526 Cloudflare/CDN origin errors.

Client errors (4xx) do not trigger recovery.

Monitor markers

Recovered requests receive a dedicated marker in the monitor list. Their details include:

• The original failed response before recovery.
• The final cached response returned to the page.