That’s exactly how the plugin is supposed to work, you can’t exclude single files. Those files aren’t part of WordPress, nor they are cached by the Dynamic cache. There’s no framework that could load the plugin when you load that file.
This said, you can modify your static cache through .htaccess:
<IfModule mod_expires.c>
<FilesMatch "\.(ext)$">
ExpiresActive On
ExpiresDefault "access 1 day"
</FilesMatch>
</IfModule>
You can modify the time it’s cached for.
Unfortunately not…
we have sometimes file inside a plugin folder used for import/export, for example:
http://www.test.it/wp-content/plugins/my-plugin/my-plugin.php – main plugin file
http://www.test.it/wp-content/plugins/my-plugin/import.php – import file
…/my-plugin/import.php is cached by Siteground Dynamic cache.
Before this wasn’t a problem…as suggested by SG support, we excluded that path from Dynamic Cache. We cannot anymore if a trailing slash is automatically added.
Any suggestion?
Just add http://www.test.it/wp-content/plugins/my-plugin/* and export everything after the trailing slash.
I think it’s a matter of the check. Could you give me the actual URL at hristo.p [at] siteground.com so I can check the headers? Or if you can see whether you’re getting x-proxy-cache: HIT (cached), or MISS / BYPASS (which means it’s dynamic). I suppose that the check field which doesn’t support files by design is returning false info. Would love to see it myself so we can patch it properly though.
Hi Hristo,
the x-proxy-cache header for that page is BYPASS.
I must purge Siteground dynamic cache in order to make the script work properly.
So the issue is related to the check field only…
Thanks for the support.
Leonardo
Yes, if you get a MISS or BYPASS this means that it’s a dynamic content. I will still give that test field some love for the next update though 🙂
