Originally Posted by Kalroth
Now if the browser cached everything, I should be able to close the browser, open it again and visit the exact same page where I only need to load the character xml. But when I open the browser and visit the same cached page, it takes just as long as the first time I loaded the page. I experience the same with Firefox, so it's not an IE7 thing. I haven't changed any cache settings on either browser either, they're using default settings.
|
That is not correct. HTTP defines different types of caching, and different policies. What you described sounds like the policy is set to no-store, which specifies caching is allowed in ram, so long as it does not hit any sort of persistent store. That should give pretty good performance after the initial origin loads occur, and for most people would have basically as good interactive experience as caching to disk. It certainly seems weird to be used in this case, but just because you are not caching things to disk does not mean there is not caching going on. For all the details checkout
RFC2616 section 14.9 (well, most of the details, there are some extensions like etags). Note that this does not mean the site performance is good, but rather that caching between sessions would only speed up the initial load, not subsequent browsing.