Why am I getting the "Document Expired/Try Again/Resend" runaround for the www.stockscores.com site, which I have been running on Firefox for years?
This is a stock charting site. I quickly run through a portfolio of stock charts every morning and again after the markets close. I started getting the "Document Expired" message yesterday on almost every chart, which slows my research down to a crawl. Today it is happening on roughly every second chart. There is nothing "sensitive" or "private" about these charts - they just display publicly available stock data. This problem does not happen with Internet Explorer.
Kaikki vastaukset (15)
Many site issues can be caused by corrupt cookies or cache.
- Clear the Cache and
- Remove Cookies Warning ! ! This will log you out of sites you're logged in to.
Type about:preferences in the address bar and press enter.
- Cookies; Select Privacy. Under History, select Firefox will Use Custom Settings. Press the button on the right side called Show Cookies. Use the search bar to look for the site. Note; There may be more than one entry. Remove All of them.
- Cache; Select Advanced > Network. Across from Cached Web Content, Press Clear Now.
If there is still a problem, Start Firefox in Safe Mode {web link} While you are in safe mode;
Type about:preferences in the address bar and press enter
Select Advanced > General. Look for and turn off Use Hardware Acceleration.
Poke around safe web sites. Are there any problems?
Then restart.
Are you using a bookmark when this happens or possibly use the Back button to go to a previous page?
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.
This doesn't explain why this started happening yesterday - after years of accessing this site through Firefox with no problems - or why it was only happening intermittently today. I've tried accessing www.stockscores.com with Internet Explorer and did not have any problems.
Did clearing cache and cookies have any effect?
You can also check the date and time and time zone in the clock on your computer: (double) click the clock icon on the Windows Taskbar.
I haven't had time to try the other suggestions. I'm just using Explorer for now.
Thanks for your help. (Both of you!)
Please check https://bugzilla.mozilla.org/show_bug.cgi?id=1060082
I belive it's a new bug from ver. 32.
Thanks - that wouldn't surprise me! I've tried some of the previous suggestions (eg. clearing cache, deleting cookies) with no lasting effect. The problem is intermittent, only happens with some sites, and does not happen on Internet Explorer. I simply switch to IE whenever it happens on Firefox.
The update to version 32 downloaded this morning but the problem is still happening. I'm using Internet Explorer until Firefox fixes this!
I don't know if this will work, but it will not hurt anything.
Open the History Manager <Control><Shift> H. In the search bar, enter the name of the site. Right click on one of the listings and select Forget About This Site. This should remove all information, including and password.
Then try again.
Thx, Fred - I'll try this the next time I use Firefox.
It is best to avoid using the Back key on pages that have forms on them or were reached via data entered in a form.
So far this has worked. Thanks very much, Fred!
Hello,
I am glad to hear that your problem has been resolved. If you haven't already, please select the answer that solves the problem. This will help other users with similar problems find the solution more easily.
Thank you for contacting Mozilla Support.
Your "Sulotion" is just like "clear cache". It works, but only for a short of time. When your cache is full again, thie problem will pop up again. So it's not an ultimate solution.
Please read https://support.mozilla.org/questions/1019567, especially my post there, and another top 10 contributor confirmed it.
If you are really care about the solution or the problem itself, please test it, confirm it and comment on Bugzilla thread bugzilla I made.
Thanks!
Muokattu
You're right, fireattack - this turned out to be a short-term solution.
I read your other posts and I agree ... this problem started happening after the upgrade to version 32.
I don't have the time or patience to mess around trying to fix stuff like this. I just switch to Internet Explorer whenever it happens with Firefox.