Safari showing older web pages

Your version of Safari is too old to work with many websites. If you don't want to upgrade the OS, use another browser such as Firefox.

Firefox

I have the identical issue, and I am running Safari Version 9.1 with El Capitan 10.11.4, although it has been happening for a long time now. This is on an iMac with 3.4 GHz Intel Core i7, 8 GB 1600 MHz DDR3 and NVIDIA GeForce GTX 680MX 2048 MB.

Certain forums that I go to always load a current page on initial visit or if I hit refresh. But if I hit the back button after reading a thread, Safari uses a cached version of the page rather than the last version visited. The cached version it uses may be a day old, even though I have visited the page many times since that copy of the page was current. Something is preventing Safari from updating its cached page each time I viist. I often have a lot of tabs open in Safari (e.g. I currently have 20 tabs in two windows).

Is this a known issue, or is it controllable by Safari preferences, or ??

Safari/Preferences/Advanced - enable the Develop menu, then go there and Empty Caches. Quit/reopen Safari and test. Then try Safari/History/Show History and delete all history items. Quit/reopen Safari and test. You can also try try Safari/Clear History…. The down side is it clears all cookies.Doing this may cause some sites to no longer recognize your computer as one that has visited the web site. Go to Finder and select your user/home folder. With that Finder window as the front window, either select Finder/View/Show View options or go command - J. When the View options opens, check ’Show Library Folder’. That should make your user library folder visible in your user/home folder. Select Library./Caches/com.apple.Safari/Cache.db and move it to the trash.

Go to Safari Preferences/Extensions and turn all extensions off. Test. If okay, turn the extensions on one by one until you figure out what extension is causing the problem.

Safari Corruption See post by Linc Davis

Hi Eric, I don't think this is related to corruption or cache. I enabled the develop menu and watched the inspector's network tab as I visited this page:

http://forum.porsche356registry.org/viewforum.php?f=1

Each time I read a thread I pressed the back button, and it took me to a cached version of the page, not the current version, which is of course dynamically updated since it tracks the threads being read. Then I pressed the refresh button, which brought up the correct, up-to-date page. The network tab showed that when I pressed the back button, the "viewforum.php" script was usually not run, and the cached status changed from no to yes. When I pressed the refresh button, viewforum.php was always run, its cached status was always no, and it took time to execute. I believe that script refreshes the page content. Can you explain the differences in behavior between pressing "back" and pressing "refresh" for the same page?

viewforum.php was always run,

Where are you seeing this?

In the network tab of the web inspector window, which has been enabled from the Develop menu.

When pressing back from a thread, often viewforum.php is not run and its cached status is yes and an out of date version of the page is displayed. Sometimes (not often) it is run, in which case the page is up-to-date. I don't pretend to understand the logic.

BTW, I clicked on the cached column so that the resources would be sorted by cached status, with status = no at top, which makes it a lot easier to see the behavior.