<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: cachebusting</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/cachebusting.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2010-02-26T12:25:24+00:00</updated><author><name>Simon Willison</name></author><entry><title>Internet Explorer Cookie Internals (FAQ)</title><link href="https://simonwillison.net/2010/Feb/26/cachebusting/#atom-tag" rel="alternate"/><published>2010-02-26T12:25:24+00:00</published><updated>2010-02-26T12:25:24+00:00</updated><id>https://simonwillison.net/2010/Feb/26/cachebusting/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://blogs.msdn.com/ieinternals/archive/2009/08/20/WinINET-IE-Cookie-Internals-FAQ.aspx"&gt;Internet Explorer Cookie Internals (FAQ)&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Grr... IE 6, 7 and 8 don’t support the max-age cookie argument, forcing you to use an explicit expiry date instead. This appears to affect the cache busting cookie pattern, where you set a cookie to expire in 30 seconds for any user who posts content and use the presence of that cookie to skip caches and/or send their queries to a master instead of slave database. If you have to use expires, users with incorrect system clocks may get inconsistent results. Anyone know of a workaround?


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/cachebusting"&gt;cachebusting&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/caching"&gt;caching&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/cookies"&gt;cookies&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/internet-explorer"&gt;internet-explorer&lt;/a&gt;&lt;/p&gt;



</summary><category term="cachebusting"/><category term="caching"/><category term="cookies"/><category term="internet-explorer"/></entry></feed>