Hi, I'm using the WP-Piwik plugin for WordPress on my site, and I'm using the option for "js/index.php" rather than "piwik.js".
However, I've found that when I test my site with YSlow, it reports this issue:
But if I change the WP-Piwik plugin to use the option "Default tracking", which means it uses http://piwik.mysite.com/piwik.js then I don't get this issue with YSlow anymore - this file is correctly cached.
So it seems that the /js/ option doesn't support being cached. I'm wondering if there is any way around this, so that I can use the /js/ option and still have it cached or given a far-future expiration date by my .htaccess file?
(The reason I want to use the /js/ option is to avoid browser-based privacy filters which attempt to block tracking.)
However, I've found that when I test my site with YSlow, it reports this issue:
Quote
There is 1 static component without a far-future expiration date:
http://piwik.mysite.com/js/
But if I change the WP-Piwik plugin to use the option "Default tracking", which means it uses http://piwik.mysite.com/piwik.js then I don't get this issue with YSlow anymore - this file is correctly cached.
So it seems that the /js/ option doesn't support being cached. I'm wondering if there is any way around this, so that I can use the /js/ option and still have it cached or given a far-future expiration date by my .htaccess file?
(The reason I want to use the /js/ option is to avoid browser-based privacy filters which attempt to block tracking.)