What Is ERR_CACHE_MISS and How Do You Fix It in Chrome and Android?

ERR_CACHE_MISS is an error showing that the browser could not find in its cache the data it expected to use to show a page. In Chrome it usually appears with the “Confirm Form Resubmission” warning when you press Back or reload a page after submitting a form. In Android apps it appears as net::ERR_CACHE_MISS. In this guide we explain the causes of the error and how to fix it as a visitor and as a developer.

What Does ERR_CACHE_MISS Mean?

The browser keeps a copy of the pages you visit in its cache; when you press Back, it shows that copy instead of downloading the page again. Pages produced by a form submission (a POST request), however, are usually not cached. When you go back, the browser cannot find a suitable copy in the cache and would have to resubmit the form to show the page. Chrome does not do that without your confirmation and shows ERR_CACHE_MISS instead. This is a safety measure: it prevents the same payment or order form from being submitted twice by accident.

Causes of the ERR_CACHE_MISS Error

• Going back to or reloading a page a form was submitted to: This is the most common cause.
• Headers that prevent caching: If the site sends Cache-Control: no-store, the browser does not keep a copy of the page.
• Corrupted browser cache or extensions: Extensions that change the cache or requests can lead to unexpected situations.
• WebView configuration in Android apps: The app lacks internet permission or its WebView cache settings are wrong.

How to Fix ERR_CACHE_MISS as a Visitor

1. Decide whether to resubmit the form: If it is a harmless form such as a search or filter, you can reload the page (F5) and choose “Continue”. If it is a payment, order or message submission, do not resubmit; check in your account or email whether the action was completed.
2. Open the page again from the address bar: Typing the address again or clicking the link again, instead of pressing Back, opens the page without the form (with a GET request).
3. Clear the cache: Press Ctrl + Shift + Delete and clear “Cached images and files”.
4. Turn off extensions: Open the site in an incognito window; if the error disappears, turn extensions off one by one to find the problem one.
5. Update the browser or reset settings: If the problem continues on many sites, update Chrome and, if needed, use Settings > Reset settings.

net::ERR_CACHE_MISS in Android Apps

If you see “Webpage not available” and net::ERR_CACHE_MISS inside an app, update the app, clear its cache under Settings > Apps, and make sure Android System WebView and Chrome are up to date.

If you are the app’s developer, the most common cause is missing internet permission in the manifest file:

<uses-permission android:name="android.permission.INTERNET" />

If the permission is correct, check the WebView cache mode (setCacheMode) and that the loaded address is correct.

A Permanent Fix for Site Owners and Developers

To keep visitors from seeing this warning, use the Post/Redirect/Get (PRG) pattern for form handling: after the form is submitted, send the visitor to a result page with a 303 or 302 redirect instead of showing the result directly. For example, in PHP:

// after the form has been processed
header('Location: /order-complete', true, 303);
exit;

The result page then opens with a normal GET request; when the visitor presses Back or reloads, the form is not resubmitted. Also review pages that send Cache-Control: no-store without need; this header should be used only on pages that really contain personal or sensitive content.

Conclusion

ERR_CACHE_MISS is usually not a fault but a warning that prevents a form from being resubmitted by accident. As a visitor, decide whether to resubmit based on what the form does, or open the page from the address bar. If you own the site, the PRG pattern keeps the warning from appearing at all.