Support » Plugin: W3 Total Cache » W3TC CDN Upload does not set expiration

  • newburns

    (@newburns)


    I am using the latest version of WordPress MU and W3TC.
    I have a self-hosted CDN (basically a CNAME into a separate directory), and the images, css, and theme files that are uploaded are missing the expiration.
    Message from Google

    The following cacheable resources have a short freshness lifetime. Specify an expiration at least one week in the future for the following resources

    1. Is it adviseable to have a CDN, even though it is the same server? I am under the impression that a browser can only load 8 items simultaneously and a self hosted CDN, at the least, allows the browser to load more things at once.

    2. I have enabled all the checkboxes in Browser Cache except for

    Prevent caching of objects after settings change
    Disable cookies for static files

    and I am using the option

    cache with max age (public, max-age="EXPIRES-SCEONDS")

    and

    Expires header lifetime:	31536000 seconds

    What am I missing?
    Again, this is multisite

    http://wordpress.org/extend/plugins/w3-total-cache/

Viewing 1 replies (of 1 total)
  • Plugin Author Frederick Townes

    (@fredericktownes)

    W3TC will attempt to create an .htaccess file on your self-hosted CDN host so that your browser caching policies can be applied. If you don’t see that file on your CDN host, then there’s likely a bug with W3TC or your server’s configuration. Typically the self-hosted CDN provides performance increases by allowing for use of a cookieless domain (making requests smaller for static files) and for browser pipelining that allow browsers to download more data at once.

Viewing 1 replies (of 1 total)
  • The topic ‘W3TC CDN Upload does not set expiration’ is closed to new replies.