WordPress.org

Forums

WP2Cloud
[resolved] Wish2: Add Cache-Control max-age (13 posts)

  1. Per Soderlind
    Member
    Posted 2 years ago #

    May I bug you with another wish? :) For wblobs (images etc), add Cache-Control max-age:time (time = option on the WP2Cloud option page).

    Samle code here: http://docs.aws.amazon.com/AmazonS3/latest/dev/UploadObjSingleOpPHP.html

    Br,
    PerS

    http://wordpress.org/extend/plugins/wp2cloud-wordpress-to-cloud/

  2. Artem Livshits
    Member
    Plugin Author

    Posted 2 years ago #

    Hi Per,

    Cloud you elaborate on the reasons for needing a configurable cache control option? The Weblob data type that WP2Cloud uses to store media files in the cloud generates a new URL every time the data changes, so there is no functional need to have an expiration policy.

  3. Per Soderlind
    Member
    Posted 2 years ago #

    Hi Artem,

    I'm planing to move my site to aws. I've have a test site at http://aws.soderlind.no/ built on your linux + mysql instance (not the yapixx instance) where I've added apc, php-fpm, nginx (with fastcgi cache and the purge cache module) and wordpress with the nginx, wp2cloud and w3 total cache plugins. I monitor the site using new relic.

    Content is distributed using cloudfront (cdn01 = wblob, cdn02 = js, css + etc ) and cloudflare.

    Tuning for speed, gtmatrix and pingdom complains that the wblob files should have a expiration time ( Cache-Control max-age: "one week or more"). w3 total cache sets the expiration time for the files on cdn02 but not for the image files in cdn01.

    Br,
    PerS

  4. Per Soderlind
    Member
    Posted 2 years ago #

    Here's the result from tools.pingdom.com: http://screencast.com/t/jG5MOhNAn1yH

  5. Artem Livshits
    Member
    Plugin Author

    Posted 2 years ago #

    Hi Per,

    Thank you for report! It looks like ClouSE doesn't set the cache control headers, so S3 uses its default expiration policy which is one hour, I believe. I filed a bug suggesting that ClouSE should set max-age to a year (or more) in the future.

  6. Per Soderlind
    Member
    Posted 2 years ago #

    Hi Artem,

    Any news on this ?

    Br,
    PerS

  7. Artem Livshits
    Member
    Plugin Author

    Posted 2 years ago #

    This feature will be available in the next release of ClouSE, hopefully within a month.

  8. Per Soderlind
    Member
    Posted 2 years ago #

    Excellent, looking forward to it.

  9. Artem Livshits
    Member
    Plugin Author

    Posted 2 years ago #

    Just released a new version of ClouSE. Now the max-age is set to one year in the future.

  10. Per Soderlind
    Member
    Posted 2 years ago #

    Thank you ! :)

  11. Per Soderlind
    Member
    Posted 2 years ago #

    Eh .. how can I update / add the max-age for existing images ? I'm using cloudfront.

  12. Artem Livshits
    Member
    Plugin Author

    Posted 2 years ago #

    Hi Per,

    ClouSE doesn't set cache control headers for existing Weblobs. You can do it manually if you don't have a lot of objects or you can use a script.

  13. Per Soderlind
    Member
    Posted 2 years ago #

    I used Bucket Explorer to change the max-age.

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • WP2Cloud
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic

Tags

No tags yet.