Welcome to WebmasterWorld Guest from 188.8.131.52
Forum Moderators: incrediBILL
there's many kinds of caches, how will u decide on the on them? yes or now for each one.
1. server cache (reverse cache)
this is nice as long as you have enough memory/hd, but u have to make the cache separate different users+guest, such Vary header?
think of making some static pages for performance? but what content can be in static page? remove all the login urls and current usernames?
2. proxy cache
this is somehow widely used by clients although may not expected by webmasters. u have no control of them, they might or might not work as standard, which may lead to problem.
3. client cache (on disk)
3.1. for user to "surf" when browser is marked as Offline
3.2. for script/css that generated by dynamically but u don't expected to be requested on each new page
4. client history cache (in memory, in IE at least)
this is REALLY nice. there's something "webdeveloping top n mistakes" or so mentioned the problem that many dynamic webpages break client's history cache, it's annoying as soon as u know what "back" is. each webdesigner can make their own "nice" back button, the only back button can be "easily get used to" is on your browser toolbar which never changes.
u may discuss on selecing caches on above, but here's my key question:
a. if u want case 3.1, u make pages private or public cachable, but how do u make sure browser do not use a cached version if user click on a link
b. if u don't want case 3.1, u may make pages "no-cache", but now how to make 4 possible?
it would be nice to cross browser.
MSDN link [msdn.microsoft.com]
HttpCachePolicy.SetAllowResponseInBrowserHistory which kill Expires header, but even don't work in IE, if HttpCachePolicy is set to NoCache (there's someone asking someone question on google without an answer)
[edited by: encyclo at 2:10 am (utc) on Dec. 14, 2005]
[edit reason] fixed sideways scroll [/edit]