Or “How to set a far future Expires header in S3 to appease the YSlow gods”. I’m working on a Ruby on Rails site that stores images and other static content on Amazon S3. We want Amazon to serve all of our images with a Cache-Control or Expires header set to a point in the very far future. This will avoid unnecessary HTTP requests on subsequent page views, making the site faster for users and cons
Updated on 4/27: Added the workaround for the bug in the Mac's flash plugin. (First things first, there is a rails plugin that automates a lot of this process. I didn't like the way it worked for a few reasons (like making swfobject.js into one big javascript variable), so I decided not to use it. PJ at GitHub mentioned that they use it, so it must not be all bad.) These are some stumbling blocks
S3SwfUpload =========== S3SwfUpload allow user uploading a file to S3 directly, so you can save the cost of uploading process in your app server. Install ======= ./script/plugin install git://github.com/GreenAsJade/s3-swf-upload-plugin.git Example ======= There is an example app showing how to use this at http://github.com/GreenAsJade/demo-s3-swf-upload/tree/master It's live at http://demo-s3-swf-
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く