Plugin Contributor
iSaumya
(@isaumya)
Hi @john53,
Reading your message it seems they are not actually enabling nginx at your server level but rather allowing you to use nginx as a proxy. In that case you really don’t need it. You will have much better cache experience with the fallback cache + Cloudflare CDN level cache.
NGINX Direct Delivery has nothing to do with the reverse-proxy NGINX powering the full-page caching.
It handles only static resources and you should totally enable it. It should not cause problems with other plugins. By the way, you have full-page caching on Cloudflare in the SG Optimizer too.
Plugin Contributor
iSaumya
(@isaumya)
Hi @hristo-sg,
If the NGINX Direct Delivery only handles the static resources then yes it definitely can be enabled. Thanks for clarifying that. 🙂
you have full-page caching on Cloudflare in the SG Optimizer too
– That’s really good. But it seems it only works over Worker mode which is not 100% free like page rules, I hope you are aware of that.
Moreover, while digging a bit I saw that you guys took that feature from this plugin and your Worker script: https://plugins.trac.ww.wp.xz.cn/browser/sg-cachepress/trunk/templates/cloudflare-worker.tpl is almost a clone of the worker script I wrote for this plugin. 😀
One more thing, as I was reading this page: https://www.siteground.com/tutorials/wordpress/sg-optimizer/cloudflare-full-page-caching-sg-optimizer/ I saw that you guys add the cache-control of s-max-age=604800, s-maxage=604800, max-age=60 exactly like we used to do and there is a mistake. You guys should have followed our changelog. The s-max-age serves absolutely no purpose and we have removed it long back (check changelog). So, just keep s-maxage=604800, max-age=60.
Also for requests not to cache it’s better to add must-revalidate in no-store, no-cache, max-age=0. Just a few things I noticed while looking around. 🙂
Yes, we are aware, workers have a free limit of 100 000 hits a day which more than enough for sies on a shared environment 🙂 Thanks for pointing out those two, I will check them out but they are there for compatibility reasons, we don’t serve only Chrome users 🙂
Plugin Contributor
iSaumya
(@isaumya)
Hi @hristo-sg,
I will check them out but they are there for compatibility reasons, we don’t serve only Chrome users
– s-maxage is a Cloudflare CDN level directive that has nothing to do with browsers. Read: https://support.cloudflare.com/hc/en-us/articles/115003206852-Understanding-Origin-Cache-Control#h_4250342181031546894839080
Please don’t mind but if you guys have done homework and research before just copy-pasting our code and features into your own plugin by just cloning & renaming them without any credit or anything you guys would have known about this. 🙂
Trust me, we have done, attribution will be added but there are only few checks that we’ve used directly, the code is far from being cloned and renamed.
Thread Starter
john53
(@john53)
Hi
Thank you both for your suggestions.
I have NGINX Direct Delivery enabled on siteground and fallback cache + Cloudflare CDN level cache on the wp cloudflare super page cache plugin.
Presumably I can ignore the comments on the plugin cache settings that refer to nginx on the browser cache and other sections?
Thank you once again
Best regards
John
Plugin Contributor
iSaumya
(@isaumya)
Hi @john53,
If your main server (which is serving the website) is not nginx based then you don’t have to worry about adding those nginx rules into your nginx.conf file.
