Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

I want to get back to my search page and have it be in cache how?

  • 5 답장
  • 15 이 문제를 만남
  • 4 보기
  • 최종 답변자: Rolf44

more options

I keep getting this when try to go back to a search page. Now I have to click try again, then resend every time. I don't think a search page is very sensitive. Can I fix this? Thanks

Rolf.

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.
I keep getting this when try to go back to a search page. Now I have to click try again, then resend every time. I don't think a search page is very sensitive. Can I fix this? Thanks Rolf. 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.

모든 댓글 (5)

more options

Are you using Startpage.com? We had another report of this, but I wasn't able to reproduce the problem. Could you take a look at this thread and see whether anything helps: Firefox 32 always gives "Document expired" every single time I hit the Back key to return to search results.

more options

Hi.

Thanks for the reply. Yes I am using startpage. The thread you linked me to said to deleting the cache. for the moment it seems to have worked.

more options

Thank you for the follow-up. A user who is researching this in detail says it occurs when Firefox's cache is full, so that makes sense as a temporary workaround.

more options

It might be better that, from the search page, right click and select Open In New . . . . This way the page is still there.

more options

Thanks. will try. when cache filled up problem returned. Maybe this will be fixed in near future update?