<?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: Apache 101 &#8211; Cache Control</title> <atom:link href="http://www.placona.co.uk/126/vps/apache-101-cache-control/feed/" rel="self" type="application/rss+xml" /><link>http://www.placona.co.uk/126/vps/apache-101-cache-control/</link> <description>ColdFusion, Ruby and General Technology</description> <lastBuildDate>Thu, 26 Jan 2012 20:51:00 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=</generator> <item><title>By: Speed up yor website &#8211; Part 1 &#124; General Techie Stuff &#124; Marcos Placona Blog</title><link>http://www.placona.co.uk/126/vps/apache-101-cache-control/comment-page-1/#comment-553</link> <dc:creator>Speed up yor website &#8211; Part 1 &#124; General Techie Stuff &#124; Marcos Placona Blog</dc:creator> <pubDate>Wed, 12 May 2010 08:55:38 +0000</pubDate> <guid
isPermaLink="false">#comment-553</guid> <description>[...] usually brings a great deal of improvement, and browser cache and compression often help a lot too, but sometimes you just need to load assets on every single [...]</description> <content:encoded><![CDATA[<p>[...] usually brings a great deal of improvement, and browser cache and compression often help a lot too, but sometimes you just need to load assets on every single [...]</p> ]]></content:encoded> </item> <item><title>By: Neil Middleton</title><link>http://www.placona.co.uk/126/vps/apache-101-cache-control/comment-page-1/#comment-219</link> <dc:creator>Neil Middleton</dc:creator> <pubDate>Thu, 30 Apr 2009 00:00:00 +0000</pubDate> <guid
isPermaLink="false">#comment-219</guid> <description>If you do this you&#039;re going to find deployments very hard as clients won&#039;t check for new files for a day after the last hit.
Ideally what you want is to use E-Tags or timestamp your files URL to force client cache (e.g image1.gif?200904301147)</description> <content:encoded><![CDATA[<p>If you do this you&#8217;re going to find deployments very hard as clients won&#8217;t check for new files for a day after the last hit.</p><p>Ideally what you want is to use E-Tags or timestamp your files URL to force client cache (e.g image1.gif?200904301147)</p> ]]></content:encoded> </item> <item><title>By: Marcos Placona</title><link>http://www.placona.co.uk/126/vps/apache-101-cache-control/comment-page-1/#comment-220</link> <dc:creator>Marcos Placona</dc:creator> <pubDate>Thu, 30 Apr 2009 00:00:00 +0000</pubDate> <guid
isPermaLink="false">#comment-220</guid> <description>Hi Neil, eTags is exactly the next topic I&#039;ll be talking about. I find that ySlow helps heaps to detect this kind of things, and to be honest, I didn&#039;t know about eTags till very recently when I decided to set up my own server.
But thanks for pointing that out. You can expect a post on eTags coming on the next few days.
Cheers</description> <content:encoded><![CDATA[<p>Hi Neil, eTags is exactly the next topic I&#8217;ll be talking about. I find that ySlow helps heaps to detect this kind of things, and to be honest, I didn&#8217;t know about eTags till very recently when I decided to set up my own server.</p><p>But thanks for pointing that out. You can expect a post on eTags coming on the next few days.</p><p>Cheers</p> ]]></content:encoded> </item> </channel> </rss>
