AMP pages not getting cached

I just checked that Cached HTML Pages list is showing AMP urls but when I check headers of any of the cached page, this is what I see in the headers. Cache was enabled using workers, if that makes it relevant.

• This reply was modified 1 year, 9 months ago by Akki.

Hi @luckyankit,
If you are using the worker mode then yes the cache for AMP pages will be bypassed as AMP pages are technically created to be auto cached by Google CDN.

Moreover, at this point I would suggest you to not using the worker mode and instead disable the worker mode and use the default page rule based caching. If the cache buster query parameter bothers you, then you can enable the new Remove Cache Buster Query Parameter option (screenshot: https://i.imgur.com/Bfjzirz.jpeg) present under the other tab.

Before implementing the new Remove Cache Buster Query Parameter option, please ensure that you read the implementation guide properly. Please add the Cache Rule no. 1 – 3 and I am sure that your issues will be resolved.

Hi, thanks a lot for sharing that, I am definitely going to try that. I have three additional queries if you can please answer:

Does Cloudflare now allows bypassing cache via cookies using cache rules on the free plan?

On the installation guide, Point 4 seemed important too; not recommending using that? I am going to remove the cache buster query though.

What is the best setting for the wp-rocket to use along with the above setup?

• This reply was modified 1 year, 9 months ago by Akki.

Hi @luckyankit,

Does Cloudflare now allows bypassing cache via cookies using cache rules on the free plan?

– Yes they does via the Cache Rules. Please read the implementation guide properly all of your queries will be resolved.

On the installation guide, Point 4 seemed important too; not recommending using that?

– Yes it is not recommended if your website uses any features that are depended on query strings. For example if your website has a search feature it is using ?s query string to do that. So, if you implement the cache rule no 4 then you any of your website features that are query string dependent will fail.

As of now the option to allow some specific query string and ignore the rest is only available in Cloudflare Business and Enterprise plan but not in Free and Pro.

Also this rule has nothing to do with removing the cache buster. Again if you read the implementation guide properly you will see after adding Cache Rule no. 1-3 you need to go inside the plugin settings page and enable the option to remove cache buster query string. After that the plugin won’t use the cache buster query string anymore.

What is the best setting for the wp-rocket to use along with the above setup?

– Whether you use this option or not, nothing changes in terms of WP Rocket setup. Please read this guide to see how you need to use WP Rocket with this plugin.

Personally I will not suggest using WP Rocket with this plugin. Instead of using WP Rocket along with this plugin you can use other plugins that are focused on static file and other optimizations. For example, using this plugin with Perfmatters or Autoptimize is a great combo, where this plugin handle the page caching and they handle the static file optimization and other optimizations.

Thank you for answering in detail.

About point 4, I understand now the query string urls, like for a simple blog, I can only think of search using query string. What else? What other queries can be there in your knowledge for a blog? About the search, I can just change the search URL, that’s easy.

I think the search query string is the most important. beside that for a normal blog I don’t think any other query string needs to be bypassed.

I modified all 4 rules in a way to make them compatible with the expression builder, and modified the hostname entry to make it compatible with sites using www. Plz check if all that is okay.

(http.host contains "example.com" and starts_with(http.request.uri.path, "/wp-admin") and starts_with(http.request.uri.path, "/wc-api/") and starts_with(http.request.uri.path, "/edd-api/") and starts_with(http.request.uri.path, "/search") and starts_with(http.request.uri.path, "/wp-json/"))

(http.host contains "example.com" and http.request.uri.path contains ".xsl" and http.request.uri.path contains ".xml" and http.request.uri.path contains ".php")

(http.host contains "example.com" and http.cookie contains "wordpress_logged_in_" and http.cookie contains "comment_" and http.cookie contains "woocommerce_" and http.cookie contains "wordpressuser_" and http.cookie contains "wordpresspass_" and http.cookie contains "wordpress_sec_" and http.cookie contains "yith_wcwl_products" and http.cookie contains "edd_items_in_cart" and http.cookie contains "it_exchange_session_" and http.cookie contains "comment_author" and http.cookie contains "dshack_level" and http.cookie contains "auth_" and http.cookie contains "noaffiliate_" and http.cookie contains "mp_session" and http.cookie contains "xf_" and http.cookie contains "mp_globalcart_" and not http.request.uri.path contains ".")

(http.host contains "example.com" and not starts_with(http.request.uri.path, "/wp-admin") and not starts_with(http.request.uri.path, "/wp-login") and not starts_with(http.request.uri.path, "/wp-json/") and not starts_with(http.request.uri.path, "/wc-api/") and not starts_with(http.request.uri.path, "/edd-api/") and not http.request.uri.path contains ".xsl" and not http.request.uri.path contains ".xml" and not http.request.uri.path contains ".php" and not starts_with(http.request.uri.path, "/search") and not http.cookie contains "wordpress_logged_in_" and not http.cookie contains "comment_" and not http.cookie contains "woocommerce_" and not http.cookie contains "wordpressuser_" and not http.cookie contains "wordpresspass_" and not http.cookie contains "wordpress_sec_" and not http.cookie contains "yith_wcwl_products" and not http.cookie contains "edd_items_in_cart" and not http.cookie contains "it_exchange_session_" and not http.cookie contains "comment_author" and not http.cookie contains "dshack_level" and not http.cookie contains "auth_" and not http.cookie contains "noaffiliate_" and not http.cookie contains "mp_session" and not http.cookie contains "xf_" and not http.cookie contains "mp_globalcart_")

Also modified comment_ cookie to does not contain. Added /search to the list.

• This reply was modified 1 year, 9 months ago by Akki.
• This reply was modified 1 year, 9 months ago by Akki.
• This reply was modified 1 year, 9 months ago by Akki.
• This reply was modified 1 year, 9 months ago by Akki.
• This reply was modified 1 year, 9 months ago by Akki. Reason: remove original domain

Hi @luckyankit,

1. If your website contains WWW then you need to change the example.com with www.example.com inside the Cache Rules.
2. Thanks for pointing out the mistake related to comment_ cookie name. Yes it is supposed to be does not contain and not not equals. I’ve fixed this issue now in the updated implementation guide. Thanks for pointing it out.
3. If you have a dedicated search page page /search you can definitely bypass that from the cache rule like you have done but you can achieve the same by mentioning that page to be bypassed from caching inside the plugin settings section. For that you didn’t have to add this cache rule.
4. Please check the implementation guide again as I have updated the guide and updated the Cache Rule 4 to ensure now it automatically whitelists the ?s search query param used by the WordPress system. So, now if you use the Cache Rule no. 4, it will not break the search functionality on your website.

Checkout the updated implementation guide. I’m sure now you can use all the Cache Rules from No. 1-4. ??