2007
2006
An IE AJAX gotcha: page caching | GreenAsh
by marco & 3 othersIt appears that IE is prone to malfunctioning, unless a document accessed through AJAX has its HTTP header set to disallow caching. Beware!
Internet Explorer and AJAX image caching woes
by mauriz & 1 otherProblèmes d'Internet Explorer à utiliser son cache
Caching Tutorial for Web Authors and Webmasters
by bader & 23 others, 1 commentThis is an informational document. Although technical in nature, it attempts to make the concepts involved understandable and applicable in real-world situations. Because of this, some aspects of the material are simplified or omitted, for the sake of clarity. If you are interested in the minutia of the subject, please explore the References and Further Information at the end.
XML.com: Doing HTTP Caching Right: Introducing httplib2
by bader & 6 othersYou need to understand HTTP caching. No, really, you do. I have mentioned repeatedly that you need to choose your HTTP methods carefully when building a web service, in part because you can get the performance benefits of caching with GET. Well, if you want to get the real advantages of GET then you need to understand caching and how you can use it effectively to improve the performance of your service.
Caching Tutorial for Web Authors and Webmasters
by benoit & 23 others, 1 commentThis is an informational document. Although technical in nature, it attempts to make the concepts involved understandable and applicable in real-world situations. Because of this, some aspects of the material are simplified or omitted, for the sake of clarity. If you are interested in the minutia of the subject, please explore the References and Further Information at the end.
2005
Caching Tutorial
by camel & 23 others, 1 comment (via)
A Web cache sits between one or more Web servers (also known as origin servers) and a client or many clients, and watches requests come by, saving copies of the responses — like HTML pages, images and files (collectively known as representations) — for itself. Then, if there is another request for the same URL, it can use the response that it has, instead of asking the origin server for it again.