\n
Create a caching rule as shown below, select \"Bypass Cache\" and place this rule at the top of the process.<\/p>\n\n\n\n
The purpose of this rule is to prevent Cloudflare from caching the admin backend, the frontend user center, the search interface and the preview interface so that it doesn't cache other people's information.<\/p>\n\n\n\n
(http.request.full_uri eq \"https:\/\/\u60a8\u7684\u57df\u540d\/wp-admin\/*\") or (http.request.full_uri eq \"https:\/\/\u60a8\u7684\u57df\u540d\/*preview=true*\") or (http.request.full_uri eq \"https:\/\/\u60a8\u7684\u57df\u540d\/\u524d\u53f0\u7528\u6237\u4e2d\u5fc3\/*\") or (http.request.full_uri eq \"https:\/\/\u60a8\u7684\u57df\u540d\/?s=*\")<\/code><\/pre>\n\n\n\n\n
\n
\n
First rule.<\/figcaption><\/figure>\n<\/div><\/div><\/div>\n<\/div><\/div>\n<\/div><\/div>\n<\/div><\/div>\n<\/div><\/div>\n<\/div><\/div>\n\n\n\n\n
4. Create a second cache rule<\/h3>\n\n\n\n\n
\n
Create a caching rule as shown below, select \"Bypass Cache\" and place this rule second in the process.<\/p>\n\n\n\n
The purpose of this rule is to enable logged in users (with login cookies) or users who have sent a comment to CDN request back to the source and provide dynamic content (DYNAMIC), ensuring that the front-end is updated in real time.<\/p>\n\n\n\n
(starts_with(http.request.full_uri, \"https:\/\/\u60a8\u7684\u57df\u540d\/\") and http.cookie contains \"wordpress_sec_\") or (starts_with(http.request.full_uri, \" https:\/\/\u60a8\u7684\u57df\u540d\/\") and http.cookie contains \"wordpress_logged_in\") or (starts_with(http.request.full_uri, \"https:\/\/\u60a8\u7684\u57df\u540d\/\") and http.cookie contains \"comment_\")<\/code><\/pre>\n\n\n\n\n
\n
\n
The second rule<\/figcaption><\/figure>\n<\/div><\/div><\/div>\n<\/div><\/div>\n<\/div><\/div>\n<\/div><\/div>\n<\/div><\/div>\n<\/div><\/div>\n\n\n\n\n
5. Create a third cache rule<\/h3>\n\n\n\n\n
\n
Create a caching rule as shown below and place this rule at the bottom of this flow.<\/p>\n\n\n\n
The purpose of this rule is to realize that unlogged-in visitors (without login cookies) accessing the site are directly provided with a CDN fully caching the site pages (HIT) without the need to go back to the source.<\/p>\n\n\n\n
(starts_with(http.request.full_uri, \"https:\/\/\u4f60\u7684\u57df\u540d\/\") and not http.cookie contains \"wordpress_sec_\" and not http.cookie contains \"wordpress_ logged_in\" and not http.cookie contains \"comment_\")<\/code><\/pre>\n\n\n\n\n
\n
\n
The third rule<\/figcaption><\/figure>\n<\/div><\/div><\/div>\n<\/div><\/div>\n<\/div><\/div>\n<\/div><\/div>\n<\/div><\/div>\n<\/div><\/div>\n<\/div><\/div>\n<\/div><\/div>\n\n\n\nSelect \"Cache eligible\" here, and the following settings can be used.Configure as you see fit<\/strong>, it is recommended to turn on the following option: Cache Spoofing Armor in order to cache static resources.<\/p>\n\n\n\n
Site Configuration<\/figcaption><\/figure>\n<\/div>\n\n\n6. Check the order of caching rules<\/h3>\n\n\n\n Please make sure that the 3 rules are sorted in the above order, you can drag or click on the arrows to re-sort the rules.<\/p>\n\n\n
\n
Sorting Demonstration<\/figcaption><\/figure>\n<\/div>\n\n\n7. Validation of the entry into force of the rules<\/h3>\n\n\n\n You can open the developer tools by pressing F12 in the InPrivate tab of your browser and check the \"cf-cache-status\" of the corresponding URL in the Network column. Under normal circumstances, you will see the following, which indicates that the configuration was successful:<\/p>\n\n\n\n
\nNot logged in: cf-cache-status:HIT<\/li>\n\n\n\n After login: cf-cache-status:DYNAMIC<\/li>\n<\/ul>\n\n\n\nIf there is a problem, check if there are any items in the \"Page Rules\" etc. that conflict with it.<\/strong><\/p>\n\n\n\nOnce this configuration is complete, you can check and refine other configurations on your own, which will not be repeated here.<\/p>\n\n\n\n
Demonstration<\/h2>\n\n\n\n This configuration can have a significant acceleration effect on unlogged-in visitors, while reducing the burden on the server.<\/p>\n\n\n
\n
Optimized speed test effect of this site<\/figcaption><\/figure>\n<\/div>\n\n\nI hope this tutorial can help webmasters in need; I also hope Cloudflare can continue to provide excellent acceleration services and develop more advanced features!<\/p>\n\n\n\n
References:<\/h3>\n\n\n\n\nhttps:\/\/developers.cloudflare.com\/cache\/how-to\/cache-rules\/<\/li>\n\n\n\n https:\/\/developers.cloudflare.com\/support\/other-languages\/%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87\/%E4%BD%BF%E7%94%A8-wordpresswoocommerce-%E7%BC%93%E5%AD%98%E9%9D%99%E6%80%81-html\/<\/li>\n<\/ul>\n\n\n\nNote: This article is the result of repeated research and practice, please respect the intellectual property rights of webmasters, reproduced with the source, thank you for your cooperation!<\/strong><\/p>","protected":false},"excerpt":{"rendered":"We can let Cloudflare automatically determine user login and comment status by determining cookies to distinguish whether to go back to the source or not. In this way to improve the visitor experience and reduce the burden on the server.
![\"\"](\"https:\/\/static.devhjz.com\/Web\/Blog\/img\/Posts\/16\/1.png\")
![\"\"](\"https:\/\/static.devhjz.com\/Web\/Blog\/img\/Posts\/16\/2.png\")
![\"\"](\"https:\/\/static.devhjz.com\/Web\/Blog\/img\/Posts\/16\/3.png\")
![\"\"](\"https:\/\/static.devhjz.com\/Web\/Blog\/img\/Posts\/16\/4.png\")
![\"\"](\"https:\/\/static.devhjz.com\/Web\/Blog\/img\/Posts\/16\/5.png\")
![\"\"](\"https:\/\/static.devhjz.com\/Web\/Blog\/img\/Posts\/16\/6.png\")
![\"\"](\"https:\/\/static.devhjz.com\/Web\/Blog\/img\/Posts\/16\/7.png\")