Q: Problem with safari's cache in ios 5

I'll ask him, but probably not. He has both of his accounts going through Mail app and usually reads them there. I'll try your suggestion and report back. Thanks so much.

@Andreas66 That makes sense. Does accepting ''always'' present a security risk?

Not necessarily a security risk, but a privacy risk, yes.

Right. I kind of see those as the same thing though! Anyway, I'm wondering if I go back to acceping from visited the fix will hold? I'll give it a try. Thanks.

As to an update, I strongly agree.  IOS 5 was a giant step backwards.  It is ironic, if Microsoft put this out it would be blasted all over the web.  Apple on the other hand escapes unscathed.

Nope, it doesnt hold!

Unfortunately retesting has confirmed what I thought may have corrected the issue, didn't.

If I had the time to further diagnose I would, but I don't. Perhaps this is something which has arisen from the introduction of tabbed browsing; and with luck it will be fixed in a patch.

Here's hoping a fix comes soon. In the mean time, it is hitting the refresh button if I happen to use the back button; or changing my navigation behaviour to use the appropriate link on the site itself to return to the previous page.

I too am experiencing this problem (iPad 1) and it's very annoying. I finally decided to try looking it up and found this thread. My cookies were set to "From visited" and still had the problem.

Having to hit the refresh button to make sure you're on the latest version of a page is ridiculous. Is Apple already missing Jobs? This seems so fundamental, yet how can it take so long for Apple to address it?

I just changed to "Always," re-booted, and will see how it performs.

I'm to the point that there is no user fix.  It's another Apple bug, they need to fix their software.

I am also experiencing this issue.  Additionally, tabbed browsing is not working correctly.  I click open in new tab and when I get finished reading the current tab and switch to the new one, I have to sit there and wait for it to load.  I just recently decided to give apple a try aftter many years running pc/ms.  Hope they will get this fixed.  Hitting back button and getting an old page and not having functional tabbed browsing is a bit concerning.  I thought after all these years of browser development that browsing wouldn't be a problem.

I posted here last week that switching from "visited" to "always" in the cookie accept option fixed my problem with Safari loading old webpages. And it had for about a week. Today I noticed that the problem was back. Such a bummer! I've also be noticing how unstable this iOS is overall. I really hope that Apple releases an update soon. I know that they are releasing an update that addresses the battery issue on the new iPhone 4S. I hope that the update also fixes the myriad other problems! As a side note, I've noticed that Lion also has some issues. Specifically when using iMovie. LOTS of bugs! It's not the iLife '11 version either (although there was at least one bug in that). I have used iMovie '11 several times before the Lion update without the rash of problems I encountered using it with Lion. Very unstable as well. It makes one wonder if both iOS 5 and Lion were rushed to market and we are expected to be in the test kitchen, so to speak. 

Changing my "Accept Cookies" to "Always" made no difference for me either. I'm still getting old pages with the Back button.

I develop webkit applications for the iOS devices. This issue is causing huge problems for me and my users  There is no logic to how it works. I can change a web page, the css file or javascript files and some make it into the device and some don't.  

It can take hours or even days for this to clear out. In many causes it makes the application unusable because some parts are loaded dynamically and the iOS5 device has cached other parts.  Then they are incompatble.  Writing web applications was supposed to remove this problem and Apple has made it not so.

My users are very frustrated and so am I.  This is a major bug and needs to be fixed ASAP.

My iPhone4s does not seem to exhibit this problem but the iPhone 4 and iPad 1/2 do.