joejamin

Thanks for the response. Yes, the preloading is working perfectly unless I change that setting. The reason I want to try it is because we have scheduled posts that don’t consistently purge the html page cache for some reason. There is an action with curl request to purge cache (using your cron job url) on a specific CPT publish/draft status change and the setting is checked to purge whole html cache on any post change in this/your plugin. If I change the setting from html only purge to whole purge it doesn’t preload. Any ideas? Appreciate it.

I’d like to not default to the “start point” but rather show no list and “no stores found” message? Any help would appreciated.

I just discovered the define to add more to the limit of preloader. So, you can disregard that question. Also, seems most of my URLs with parameters are getting cache hits so I think I’m all good here. Thanks!

Got it. Where are the hours/settings stored in the database? Can’t seem to figure it out. Thanks!

Really appreciate your responses! Thank you so much! My final question: What is the best way to handle the browser cache TTL so if someone happens to prefetch a url and it’s stored in “disk cache”, they get a fresh copy when it’s purged or expires. Right now we have cache-control “max-age=86400” to direct NGINX page caching on the server (at the hosts direction). Does it make sense to do this maybe?

max-age=60
s-max-age=86400

or is it not needed?

Thanks! Still wondering are these prefetch requests cached by Cloudflare if cache everything/APO is active even if the page isn’t actually visited?

Never mind on the prefetch issue – I see it in the page once I visit it.

• This reply was modified 3 years ago by joejamin.

Thanks for the replies! With Cloudflare APO for example it ignores utm parameters in the url and caches base url. Also Nginx server level caching often does this as well I’ve seen. Will have to try another solution. Appreciate the help ??

Hi Patrick – What I’m trying to achieve is to actually ignore the string and serve the base URL. Does that make sense? They visit “/page/?s=1” and they get the cached page for “/page/” rather than needing the URL with the unique parameter cached individually each time.

Thank you!