darren at darrenduncan
Nov 18, 2011, 7:53 PM
Post #5 of 9
Re: Use with Amazon CloudFront CDN (for images, PDFs, etc.)
[In reply to]
The company I work with, ChargeSmart (who is also hiring Perl developers, and
already has several CPAN authors including myself and Jon Swartz), also uses
We currently get around the old versions problem by putting a version number in
the urls of each static media element, and incrementing it when that changes.
Although not many media elements change but rather get replaced, so they have
different file names, and no version number increment needed.
The key thing is that each distinct media item has a distinct url, however it is
accomplished, and then CloudFront will do the right thing.
-- Darren Duncan
Darren Embry wrote:
> I work for a company (rfxtechnologies.com) that uses Bricolage to
> manage various clients' web sites, at least one of which is quite
> media-heavy. We want to use Amazon CloudFront as our CDN for almost
> everything except HTML pages: images, PDFs, stylesheets, etc. We use
> Amazon S3 buckets for storage, and I've done some of the work to
> integrate the S3 mover into Bricolage for version 2.1.0.
> Our problem is that when publishing a new version of a file, old
> versions of that file are still cached at the CDN endpoints for quite
> some time. Potential solutions: