Interestingly, the cache control header doesn't appear in the "view source" of the webpage. I don't know what this means.
Nevertheless, the fix described in the article does work. So cache control does play a role somehow. At any rate, I've decided that the correct resolution is to require the user to update his browser. This is, after all, a browser bug -- that's why there's a hotfix. Thanks, Richard On Oct 24, 3:04 pm, Anthony <[email protected]> wrote: > On Monday, October 24, 2011 12:17:07 PM UTC-4, horridohobbyist wrote: > > > Actually, the more specific issue is that web2py probably sends a > > "Cache-control:no-store" or "Cache-control:no-cache" header... > > Can you confirm the specific headers that web2py is sending?
