From: SourceForge.net <no...@so...> - 2009-02-12 00:03:54
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6404566 By: sroussey An additional thing: Cloundfront does not do automated gzip/deflate compression. So... in order to have fast Javascript and CSS files actually get delivered from Cloudfront *quickly*, we need to upload a precompressed file. However the "Content-Encoding: gzip" header must be set for file when put to s3. The quick and dirty is to add an: extra_header["Content-Encoding"]="gzip" when the file name ends in .gz -- that is the quick fix at least. The content-type should be determined from the extension of the filename without the .gz appended (e.g., 'something.js.gz' would get "Content-Type: application/x-javascript" and "Content-Encoding: gzip"). Thanks! With these improvements, using s3cmd to manage S3/CloudFront will become a real possibility! PS: It would help to have arbitrary headers added so these things could be done and tested before it becomes part of the core s3cmd... ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=618865 |