<?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: FrontEnders</title>
	<atom:link href="http://imgiseverything.co.uk/articles/frontenders/feed/" rel="self" type="application/rss+xml" />
	<link>http://imgiseverything.co.uk/articles/frontenders/</link>
	<description>Manchester web designer Phil Thompson</description>
	<lastBuildDate>Mon, 28 Nov 2011 11:34:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Howie</title>
		<link>http://imgiseverything.co.uk/articles/frontenders/#comment-112011</link>
		<dc:creator>Howie</dc:creator>
		<pubDate>Thu, 15 Apr 2010 14:34:01 +0000</pubDate>
		<guid isPermaLink="false">http://imgiseverything.co.uk/?p=3648#comment-112011</guid>
		<description>Phil

Thanks for sharing your experience with dealing with a popular site, and setting up Amazon S3. I can&#039;t help but think that, with the traffic stats you quote, S3 is overkill. With correct caching, this sort of load should not ber an issue.

I took a quick look at the site. The page itself has a max-age of zero and no E-Tag/If-Modified since header . Basically, you&#039;re telling the browser and any proxy/caching servers not to cache the page. If you look at the headers provided by the assets now on S3 they do have these headers.

A few lines in your Apache .htaccess fiel might well have done the trick

http://www.askapache.com/htaccess/caching-tutorial-for-webmasters.html</description>
		<content:encoded><![CDATA[<p>Phil</p>
<p>Thanks for sharing your experience with dealing with a popular site, and setting up Amazon S3. I can&#8217;t help but think that, with the traffic stats you quote, S3 is overkill. With correct caching, this sort of load should not ber an issue.</p>
<p>I took a quick look at the site. The page itself has a max-age of zero and no E-Tag/If-Modified since header . Basically, you&#8217;re telling the browser and any proxy/caching servers not to cache the page. If you look at the headers provided by the assets now on S3 they do have these headers.</p>
<p>A few lines in your Apache .htaccess fiel might well have done the trick</p>
<p><a href="http://www.askapache.com/htaccess/caching-tutorial-for-webmasters.html" rel="nofollow">http://www.askapache.com/htaccess/caching-tutorial-for-webmasters.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Thompson</title>
		<link>http://imgiseverything.co.uk/articles/frontenders/#comment-112012</link>
		<dc:creator>Phil Thompson</dc:creator>
		<pubDate>Thu, 15 Apr 2010 13:59:34 +0000</pubDate>
		<guid isPermaLink="false">http://imgiseverything.co.uk/?p=3648#comment-112012</guid>
		<description>Thanks for the info Howie, I too felt that Amazon S3 was overkill but everything else didn&#039;t seem to work. (although admittedly I didn&#039;t try modifying the headers). However, I&#039;m glad I tried out Amazon S3 and worked out how it works so when a project comes a long that truly does need it I won&#039;t be flummoxed by it.</description>
		<content:encoded><![CDATA[<p>Thanks for the info Howie, I too felt that Amazon S3 was overkill but everything else didn&#8217;t seem to work. (although admittedly I didn&#8217;t try modifying the headers). However, I&#8217;m glad I tried out Amazon S3 and worked out how it works so when a project comes a long that truly does need it I won&#8217;t be flummoxed by it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

