CheckWebsiteNow

Other browser errors

ERR_CACHE_MISS

The page needs information you entered earlier to be sent again.

Quick answer

You went back or reloaded a page that was the result of a form. The browser does not have a stored copy and asks before sending the form again.

When to wait: No waiting needed; decide whether to resend.

If you are visiting the website

  1. Think before resending The browser is asking whether to send a form again. Resending can repeat an order, a booking or a payment.
  2. Check whether the first attempt worked Look for a confirmation email, an order number in your account or a pending charge in your banking app. If you find one, do not send the form again.
  3. Open the page fresh Go to the page through the site's menu or by typing the address, instead of using Back or Reload. This loads a normal page without resending anything.
  4. Resend only harmless forms For a search, a filter or a simple lookup, sending again is harmless. Then confirm the browser's prompt or reload and continue.
  5. If it appears on normal pages, clear this site's data When ERR_CACHE_MISS shows up on pages without any form, stored data for this one site may be damaged. Clear only this site, then update your browser.
    Windows
    Chrome: click the site-information icon left of the address > Cookies and site data > Manage on-device site data > delete. Edge: Settings and more > Settings > Cookies and site permissions > Manage and delete cookies and site data > See all cookies and site data > search the site > delete.
    macOS
    Chrome: click the site-information icon left of the address > Cookies and site data > Manage on-device site data > delete. Edge: same path as on Windows.
    Android
    Chrome: tap Page info at the left of the address bar > Cookies and site data > Delete.

If you run the website

  1. Redirect after every form post After a successful POST, answer with a 303 See Other redirect to a confirmation page. Back and Reload then only repeat a harmless GET request.
  2. Block duplicate orders on the server Give each order or payment form a one-time token (an idempotency key) and reject a second submission with the same token. Then an accidental resend cannot charge twice.
  3. Use GET for searches and filters Forms that only read data should use GET. Results can then be bookmarked, reloaded and shared without any resend prompt.
  4. Show a clear confirmation Put the order number and status on the confirmation page and in an email. Visitors who are unsure can then check instead of resending.

What this error is not

It is not a broken website and not a connection problem. The browser is protecting you from sending the same form twice.

Nothing has been sent again yet. You decide.

Why the browser asks first

Forms that place orders or payments are usually sent with a POST request (a request that changes something on the server). Repeating it could repeat the action.

When the browser has no stored copy of the result page, it stops and asks you first.

For developers: Post/Redirect/Get

After processing a POST, reply with 303 See Other pointing to a result page that is fetched with GET. Back and Reload then only repeat the harmless GET, and normal visitors stop seeing ERR_CACHE_MISS.

Chromium uses this code (net error -400) when the cache has no entry for the requested page.

Common questions

Will I be charged twice if I send the form again?

You might, if the shop does not block duplicates. Check for a confirmation email, an order number or a bank notification first, and contact the shop if you are unsure.

Why does this happen after pressing Back?

The page you went back to was created by a form. The browser has no stored copy, so going back would mean sending the form again.

Can clearing my cache fix ERR_CACHE_MISS?

Usually not, because the message is about a form, not a damaged cache. If it appears on ordinary pages, clearing this one site's data and updating the browser is worth a try.

Is the information I typed lost?

If you open the form fresh, you may need to type it again. Anything you already sent successfully stays with the website.

Likely causes

  • Common You pressed Back or Reload after submitting a form. (Your side)
  • Sometimes The site shows form results without a redirect afterwards. (Website side)

What to avoid

  • Do not resend a payment form without checking whether the first one went through.

Is the website down? Check it now

One measurement point. Results explain what we saw, not a worldwide verdict.

Sources

Last reviewed: