If you apply frequent CSS or JS tweaks to the site without changing the name of the script files then you probably don’t want to use far future expiry header on them. If you make changes to the files then empty the cache then it will be all good for new visitors but old visitors who already have a cached copy of the static file (which is not expired) will continue to see the old file (Thats basically what you are telling the browser to do by specifying far future expiry). If you have made a lot of changes to a CSS or JS file then the technique is to change the name of the script so it becomes a new static resource.

Yop Polls

Comments are closed.