Closed Bug 1144002 Opened 11 years ago Closed 11 years ago

"Document Expired" om Startpage.com

Categories

(Firefox :: Untriaged, defect)

36 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1065234

People

(Reporter: mozilla15, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:36.0) Gecko/20100101 Firefox/36.0 Build ID: 20150222232811 Steps to reproduce: NOTE: Copied from Bug report that was incorrectly closed by someone who apparently has little clue or little desire to actually assist users. User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; InfoPath.3; .NET4.0E; rv:11.0) like Gecko Steps to reproduce: When the cache reaches its maximum allotment, use https://startpage.com and search for something. Navigate away from the results page either forward or backward and then return to the results page to find "Document Expired." It is worth noting the bug does NOT occur while the cache is not full. Also does not occur at all with previous versions. Actual results: Actual results: The results page is replaced with a "Problem Loading Page" error page stating, "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. Expected results: Expected results: Expected result is to return to viewing the search results and continue browsing them.
It is easy to actually reopen a bug or edit it (except for comment #0, but there is "User Story" now), so creating a complete copy of an existing recent bug is usually not useful (and when it is, there is a "Clone This Bug" link). The original bug marked duplicate of bug 1060082, which had been marked duplicate of bug 1079789.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.