Comments for Sanity Software Wisdom

Comment on Cache-Control Header for Amazon S3 by Keaka Jackson

Keaka Jackson — Mon, 23 Jun 2008 17:34:00 +0000

It’s been a while, but I believe you include a regular HTTP header in your HTTP PUT request. So wherever your PHP class generates the actual request to Amazon, you’d add a Cache-Control header to the request.

This “Getting Started Guide” has a “Writing an Object” section with PHP sample code you might be able to use:
http://docs.amazonwebservices.com/AmazonS3/2006-03-01/gsg/

Comment on Cache-Control Header for Amazon S3 by Travis

Travis — Sat, 21 Jun 2008 09:58:08 +0000

Do you happen to know the procedure and in what API method the header is ultimately being set so that when the object is put to S3 it has that header stored? I am using a PHP class which works well but I can’t figure out how to get my own custom headers (such as cache-control) to be included with the file…

Comment on Cache-Control Header for Amazon S3 by Keaka Jackson

Keaka Jackson — Wed, 18 Jun 2008 20:42:24 +0000

I mainly only use s3 for images, so I haven’t had to deal with serving gzipped assets yet.

Comment on Cache-Control Header for Amazon S3 by Joe Martinez

Joe Martinez — Wed, 18 Jun 2008 02:54:48 +0000

What do you do about gzipping your s3 assets, or do you only use s3 for images?

Comment on Amazon SimpleDB by Tom the Golf Pro

Tom the Golf Pro — Mon, 17 Dec 2007 06:45:45 +0000

Bah! Who needs SimpleDB when you could be out golfing?

Comment on Cache-Control Header for Amazon S3 by The Whiny Nil » Blog Archive » LINK: Cache-Control Header for Amazon S3

Wed, 31 Oct 2007 14:12:46 +0000

[...] Cache-Control Header for Amazon S3Amazon provides an option for specifying the Cache-Control header, but we use the AWS::S3 gem and the attachment_fu plugin for uploading our files to S3. The gem and plugin don’t provide a convenient way to set the Cache-Control header. My solution is to enhance the behavior of the store() method within the AWS::S3 gem so that it always specifies a Cache-Control header of 10 years if another value is not specified. [...]

Comment on Cache-Control Header for Amazon S3 by Adrian B. Danieli

Adrian B. Danieli — Thu, 13 Sep 2007 00:40:52 +0000

Nice. I wanted to add "Expires" as well (I know, old school) so here's a tweaked version that does it. This version forces the headers, and uses symbolized keys.

require 'aws/s3'

# Adds expiration headers to all stored S3 objects through duck-punching.
# Based on Keaka Jackson's original work.
#
module AWS::S3
  class S3Object
    class << self
      MAX_AGE = 8.years
      def store_with_cache_control(key, data, bucket = nil, options = {})
        options[:cache_control] = "max-age=#{MAX_AGE.to_i}"
        options[:expires]       = MAX_AGE.from_now.httpdate
        store_without_cache_control(key, data, bucket, options)
      end
      alias_method_chain :store, :cache_control
    end
  end
end

# To update existing photos, run this in production script/console:
#
# Photo.find(:all).each do |p|
#   s3 = AWS::S3::S3Object.find(p.full_filename, 'bucketname')
#   s3.save(:access => :public_read) unless s3.cache_control && s3.expires
# end