Join us to show up for other Firefox users 🦊. Earn fun badges and Mozilla swag vouchers! Find out more: https://mzl.la/askafox150

Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

When backspacing, will frequently not load the previous page. Below is the error message I continue to recive.

  • 2 Antworten
  • 1 hat dieses Problem
  • 249 Aufrufe
  • Letzte Antwort von gstarnes
  • Archiviert

Document Expired

This document is no longer available.

The requested document is not available in Firefox's cache.

   As a security precaution, Firefox does not automatically re-request sensitive documents.
   Click Try Again to re-request the document from the website.
Document Expired This document is no longer available. The requested document is not available in Firefox's cache. As a security precaution, Firefox does not automatically re-request sensitive documents. Click Try Again to re-request the document from the website.

Alle Antworten (2)

You can get a "document has expired" message if you use the Back button or a bookmark to go back to a specific page and the web site has instructed Firefox not to cache the page. Firefox tries to retrieve the page from the server, possibly by sending POST data that is no longer valid. In such a case best is to open links from such a page in a new tab/window by middle-clicking a link to avoid using the Back button, but instead close the tab to return to the previous tab.

Been using the same programs for years and this is a new issue. Working with the backspace button has always worked in the past. It's happening in multiple programs on two separate computers.

Is there a way to instruct the server to allow Firefox to cache pages? Although I don't think that's the issue because my work-around for this has been to resend the page and it pops up. Thanks