<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Caching and Wordpress</title>
	<atom:link href="http://www.kiwiblog.co.nz/2008/09/caching_and_wordpress.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.kiwiblog.co.nz/2008/09/caching_and_wordpress.html</link>
	<description>DPF&#039;s Kiwiblog - Fomenting Happy Mischief since 2003</description>
	<lastBuildDate>Sun, 21 Mar 2010 10:45:55 +1300</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: labrator</title>
		<link>http://www.kiwiblog.co.nz/2008/09/caching_and_wordpress.html#comment-490410</link>
		<dc:creator>labrator</dc:creator>
		<pubDate>Sat, 27 Sep 2008 21:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.kiwiblog.co.nz/?p=27452#comment-490410</guid>
		<description>From what I can tell, it&#039;s not a problem with the page, it&#039;s a problem with the headers being set on the image on the way out. This is a server configuration issue and it&#039;s unlikely you can change it, although WordPress pros may know better. 

Each image you&#039;re uploading has an expires header set 1 week in the future. This is a common feature on high bandwidth sites to conserve said bandwidth. To get around this you could either wrap the serving of the image in a custom PHP file and set your own expires headers, or you could get the consumers of your images to link to the file with a timestamped querystring. Typically if any file has a different querystring, browsers will treat it as a separate file and get it again, so if you keep changing the querystring, they&#039;ll keep getting it.

Try like this:
imagename.gif?t=&lt;? echo time(); ?&gt;</description>
		<content:encoded><![CDATA[<p>From what I can tell, it&#8217;s not a problem with the page, it&#8217;s a problem with the headers being set on the image on the way out. This is a server configuration issue and it&#8217;s unlikely you can change it, although WordPress pros may know better. </p>
<p>Each image you&#8217;re uploading has an expires header set 1 week in the future. This is a common feature on high bandwidth sites to conserve said bandwidth. To get around this you could either wrap the serving of the image in a custom PHP file and set your own expires headers, or you could get the consumers of your images to link to the file with a timestamped querystring. Typically if any file has a different querystring, browsers will treat it as a separate file and get it again, so if you keep changing the querystring, they&#8217;ll keep getting it.</p>
<p>Try like this:<br />
imagename.gif?t=&lt;? echo time(); ?&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rex Widerstrom</title>
		<link>http://www.kiwiblog.co.nz/2008/09/caching_and_wordpress.html#comment-490306</link>
		<dc:creator>Rex Widerstrom</dc:creator>
		<pubDate>Sat, 27 Sep 2008 04:09:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.kiwiblog.co.nz/?p=27452#comment-490306</guid>
		<description>Okay that makes even less sense unless I explain I&#039;m suggesting that go into the tags on the pages of any blog &lt;i&gt;displaying&lt;/i&gt; the graphic, not the one on which it&#039;s hosted. And that it works client-side by telling the browser to reload a fresh copy of the page and its content every time it visits (which slightly degrades performance, I know).

Unless you use Flash *shudder*. I think I saw this done via DHTML once. If I could shake of this spring flu I might remember where :-/</description>
		<content:encoded><![CDATA[<p>Okay that makes even less sense unless I explain I&#8217;m suggesting that go into the tags on the pages of any blog <i>displaying</i> the graphic, not the one on which it&#8217;s hosted. And that it works client-side by telling the browser to reload a fresh copy of the page and its content every time it visits (which slightly degrades performance, I know).</p>
<p>Unless you use Flash *shudder*. I think I saw this done via DHTML once. If I could shake of this spring flu I might remember where :-/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rex Widerstrom</title>
		<link>http://www.kiwiblog.co.nz/2008/09/caching_and_wordpress.html#comment-490298</link>
		<dc:creator>Rex Widerstrom</dc:creator>
		<pubDate>Sat, 27 Sep 2008 03:50:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.kiwiblog.co.nz/?p=27452#comment-490298</guid>
		<description>Well there&#039;s always &lt;meta HTTP-EQUIV=&quot;Pragma&quot; CONTENT=&quot;no-cache&quot;&gt; in the metatags part of the page header (assuming there&#039;s nothing else you can do, because that&#039;s not always respected by browsers, though I believe adding &lt;meta http-equiv=&quot;expires&quot; content=&quot;0&quot;&gt; as well captures the majority).

Now no doubt someone who knows Wordpress (I haven&#039;t a clue) is about to come along and make me look like a twat. Oh well...</description>
		<content:encoded><![CDATA[<p>Well there&#8217;s always &lt;meta HTTP-EQUIV=&#8221;Pragma&#8221; CONTENT=&#8221;no-cache&#8221;&gt; in the metatags part of the page header (assuming there&#8217;s nothing else you can do, because that&#8217;s not always respected by browsers, though I believe adding &lt;meta http-equiv=&#8221;expires&#8221; content=&#8221;0&#8243;&gt; as well captures the majority).</p>
<p>Now no doubt someone who knows Wordpress (I haven&#8217;t a clue) is about to come along and make me look like a twat. Oh well&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scrubone</title>
		<link>http://www.kiwiblog.co.nz/2008/09/caching_and_wordpress.html#comment-490220</link>
		<dc:creator>scrubone</dc:creator>
		<pubDate>Fri, 26 Sep 2008 22:36:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.kiwiblog.co.nz/?p=27452#comment-490220</guid>
		<description>You should correct the post - it reads wordpress.org :)

Have you tried putting the actual file on this site, and including a reference to it on that one?</description>
		<content:encoded><![CDATA[<p>You should correct the post &#8211; it reads wordpress.org <img src='http://www.kiwiblog.co.nz/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Have you tried putting the actual file on this site, and including a reference to it on that one?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Farrar</title>
		<link>http://www.kiwiblog.co.nz/2008/09/caching_and_wordpress.html#comment-490214</link>
		<dc:creator>David Farrar</dc:creator>
		<pubDate>Fri, 26 Sep 2008 22:27:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.kiwiblog.co.nz/?p=27452#comment-490214</guid>
		<description>The problem is this is hosted by wordpress.com, not hosted on a server I control.</description>
		<content:encoded><![CDATA[<p>The problem is this is hosted by wordpress.com, not hosted on a server I control.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.kiwiblog.co.nz/2008/09/caching_and_wordpress.html#comment-490205</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Fri, 26 Sep 2008 22:08:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.kiwiblog.co.nz/?p=27452#comment-490205</guid>
		<description>Look up WP Super Cache. Probably need to run it as a cron job on the server.</description>
		<content:encoded><![CDATA[<p>Look up WP Super Cache. Probably need to run it as a cron job on the server.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
