Comments on: Do’s and Dont’s for scaleable image hosting

By: marshn

marshn — Fri, 28 May 2010 02:58:45 +0000

Thanks for the quick response. Thats pretty much what I thought. Just spent an hour looking into it and your post here was the only glimmer of hope that it was possible. I think I’ll forgo the dynamic image sizing for now.

By: admin

admin — Fri, 28 May 2010 02:44:03 +0000

In this example I’m only using S3 as the original data store, not as the CDN, so the 404 comes from the CDN server.

Unfortunately you couldn’t use S3 for the CDN with this “poor man’s CDN” method. You’d have to pre-generate the image thumbnails and put them on S3 first as there’s no way to add .htaccess rewrite rules to S3.

By: marshn

marshn — Fri, 28 May 2010 02:30:43 +0000

In order to determine if the image file exists at first, how exactly did you manage to handle the 404 response from Amazon S3?

By: Managed Hosting

Managed Hosting — Sat, 30 Aug 2008 17:37:46 +0000

Hi mate , great post ! I would like to subscribe to your blog, please tell me where can i subscribe. Thanks !

By: chris

chris — Wed, 23 Apr 2008 01:43:28 +0000

Bingo! Glad that’s worked for you Jon

By: yongfook

yongfook — Sun, 20 Apr 2008 06:23:43 +0000

Implemented the first trick on OSF – I was serving images via a script which handled caching, but of course as you said it’s no point having the script handle this if the server can already tell you if a file exists or not. So now, if the file exists I serve the file normally, if not I serve the image via the script (which then creates the file for next time) – brilliant! Things are noticeably more snappy now.

Cheers
Jon