Hi @colmtroy,
1.) I’m using worker mode (and it’s working great). I assume these settings don’t apply in worker mode? (at my origin I also have nginx w/ Fastcgi cache running rather than your fallback).
https://i.imgur.com/RLRgWnD.png
The settings you have shown in the screenshot above, do apply even when you are using Worker mode. All settings you can see after enabling worker mode applies to the worker mode.
On another note the reason we don’t recommend using fast cgi cache or other things is because when you are using the plugin’s fallback cache it is full control over the cache, i.e. when you update posts, pages, regenerating cache for those pages and related pages etc. But that is not the chase with server-level caching. Also server-level caching most of the times doesn’t generate a good HTML disk cache. Using the plugin fallback cache means the plugin can handle all caching situations. That’s all.
2.) Is there anything special required to ensure REST API calls are NOT served from cache in worker mode?
– You mean https://example.com/wp-json/*
routes, right? If so, then yes. But as I have said in your amazing review. This will be fixed in the upcoming release of the plugin with an updated worker code. If you mean any other API endpoints, do share the endpoint example URL.
3.) Does this plugin rely on any CF Page Rules to be setup in Cloudflare itself when in worker mode?
– When you are using the worker mode the CF page rule of Cache Everything
is not being used. You can basically use the page rule mode or the worker mode. When you are using the worker mode, the whole caching logic is managed by the worker. So, no Cache Everything
page rules. But you can still use page rules for forwarding URLs or something if you want or you can handle everything via the overwritten worker script. ??
Thanks and keep up the great work. I plan on writing up a tutorial in the near future ??
– Thank you so much. Highly looking forward to it. ??
Hope this helps. ??
-
This reply was modified 4 years, 1 month ago by iSaumya.