diff --git a/public/__redirects b/public/__redirects index 916b678fc35f2c..03c94d84f9b325 100644 --- a/public/__redirects +++ b/public/__redirects @@ -1454,9 +1454,10 @@ /support/third-party-software/content-management-system-cms/using-cloudflare-with-bigcommerce/ /cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/bigcommerce/ 301 /support/third-party-software/content-management-system-cms/how-do-i-add-a-wordpress.com-custom-domain-mapping-site-to-cloudflare/ /support/third-party-software/content-management-system-cms/wordpress.com-and-cloudflare/ 301 /support/third-party-software/content-management-system-cms/how-do-i-use-wordpress-multi-site-wpmu-with-cloudflare/ /automatic-platform-optimization/ 301 -/support/third-party-software/content-management-system-cms/modified_drupal/ /support/third-party-software/content-management-system-cms/caching-html-with-drupal/ 301 +/support/third-party-software/content-management-system-cms/modified_drupal/ /cache/how-to/cache-rules/ 301 /support/third-party-software/content-management-system-cms/using-cloudflare-with-wix-website-builder/ /dns/manage-dns-records/reference/vendor-specific-records/#wix 301 /support/third-party-software/content-management-system-cms/wordpress.com-and-cloudflare/ /support/third-party-software/content-management-system-cms/wordpresscom-and-cloudflare/ 301 +/support/third-party-software/content-management-system-cms/can-i-use-wordpress-caching-plugins-like-super-cache-or-w3-total-cache-w3tc-with-cloudflare/ /cache/how-to/cache-rules/ 301 /support/more-dashboard-apps/cloudflare-scrape-shield/what-does-scrape-shield-do/ /waf/tools/scrape-shield/ 301 /support/third-party-software/others/how-do-i-get-cloudflare-to-work-with-vaultpress/ /automatic-platform-optimization/ 301 /support/third-party-software/others/can-i-use-cloudflare-and-varnish-together/ /rules/snippets/ 301 @@ -1536,6 +1537,12 @@ /support/account-management-billing/understanding-cloudflare-sales-tax/ /billing/sales-tax/ 301 /support/account-management-billing/ /support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account/ 301 /support/account-management-billing/cannot-locate-dashboard-account/ /support/troubleshooting/general-troubleshooting/cannot-locate-dashboard-account/ 301 +/support/third-party-software/content-management-system-cms/caching-static-html-with-wordpresswoocommerce/ /cache/how-to/cache-rules/ 301 +/support/third-party-software/content-management-system-cms/caching-html-with-drupal/ /cache/how-to/cache-rules/ 301 +/support/third-party-software/content-management-system-cms/using-cloudflare-and-drupal-five-easy-recommended-steps/ /cache/how-to/cache-rules/ 301 +/support/third-party-software/content-management-system-cms/cloudflare-and-joomla-recommended-first-steps/ /cache/how-to/cache-rules/ 301 +/support/third-party-software/e-commerce/caching-static-html-with-magento-business-and-enterprise-only/ /cache/how-to/cache-rules/ 301 +/support/third-party-software/e-commerce/ /cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/ 301 # r2 /r2/platform/s3-compatibility/api/ /r2/api/s3/api/ 301 @@ -2426,4 +2433,4 @@ /containers/scaling-and-routing /containers/platform-details/scaling-and-routing 301 /containers/architecture /containers/platform-details/architecture 301 /containers/durable-object-methods /containers/platform-details/durable-object-methods 301 -/containers/platform-details /containers/platform-details/architecture 301 \ No newline at end of file +/containers/platform-details /containers/platform-details/architecture 301 diff --git a/src/content/docs/rules/page-rules/reference/additional-reference.mdx b/src/content/docs/rules/page-rules/reference/additional-reference.mdx index a8ac33e984131c..79e3bd718fda65 100644 --- a/src/content/docs/rules/page-rules/reference/additional-reference.mdx +++ b/src/content/docs/rules/page-rules/reference/additional-reference.mdx @@ -28,11 +28,7 @@ Limitations include: - 12 wildcards per cookie regex - 1 wildcard in between each `|` in the cookie regex -To learn how to configure **Bypass Cache on Cookie** with a variety of platforms, review these articles: - -- [Caching Static HTML with WordPress/WooCommerce](/support/third-party-software/content-management-system-cms/caching-static-html-with-wordpresswoocommerce/) -- [Caching Static HTML with Magento (Business and Enterprise only)](/support/third-party-software/e-commerce/caching-static-html-with-magento-business-and-enterprise-only/) -- [Customize cache](/cache/concepts/customize-cache/) +To learn how to configure **Bypass Cache on Cookie** with a cache rule, refer to [Bypass Cache on Cookie](/cache/how-to/cache-rules/examples/bypass-cache-on-cookie/). :::note diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/caching-html-with-drupal.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/caching-html-with-drupal.mdx deleted file mode 100644 index d36521bc092a7e..00000000000000 --- a/src/content/docs/support/third-party-software/content-management-system-cms/caching-html-with-drupal.mdx +++ /dev/null @@ -1,62 +0,0 @@ ---- -pcx_content_type: troubleshooting -source: https://support.cloudflare.com/hc/en-us/articles/115002911927-Caching-HTML-with-Drupal -title: Caching HTML with Drupal - ---- - -import { DashButton } from "~/components"; - -## Overview - -:::note - -Customers in all Cloudflare plans can cache HTML files using Cloudflare Page Rules. However, only customers in the Business and Enterprise plans are able to bypass HTML caching whenever a cookie is sent with a *Bypass Cache on Cookie* setting using Cloudflare Page Rules. -::: - -You can [cache HTML of inactive users](https://blog.cloudflare.com/caching-anonymous-page-views/) and static content including likes, images, scripts, and stylesheets when using Drupal with Cloudflare by using the *Cache Everything* **Page Rule** with **Bypass Cache on Cookie** enabled. - -*** - -## Enable Browser Cache TTL - -To avoid browser cache collisions, you must first enable Bypass Cache on Cookie in the Cloudflare dashboard. To do this, - -1. In the Cloudflare dashboard, go to the **Caching** page. - - - -2. Under **Browser Cache TTL**, choose **Respect Existing Headers**. - -Now, you can configure the *Bypass Cache on Cookie* setting using Cloudflare **Cache Rules**.  - -*** - -## Set Bypass Cache on Cookie - -When the *Bypass Cache on Cookie* page rule matches the criteria we set, Cloudflare will cache static images and other files, without caching HTML. To configure *Bypass Cache on Cookie* using **Cache Rules**,  - -1. In the Cloudflare dashboard, go to the **Rules** page. - - - -2. Select **Create Page Rule** button and enter your domain. In the example below, the domain is [www.orangeclouded.com](http://www.orangeclouded.com).  - -3. Configure the Page Rules settings as follows: - -* use the *\** wildcard operator on the Drupal installation path to match the entire domain -* set the Cache Level to Cache Everything -* text, set *Bypass Cache on Cookie* rule for the Drupal variables. This rule will override the *Cache Everything* rule when a user is logged into Drupal -* set the *Edge Cache TTL* setting to determine how long a Cloudflare cache server should store cached files. - -If you use additional cookies in your Drupal site, you must ensure these are in the Regex statement: *SESS.\*|phpsessid=.\** - -![The Create a Page Rule dialog with the Cache Level set to Cache Everything, Bypass Cache on Cookie set to Drupal variables, and Edge Cache TTL set to a month.](~/assets/images/support/page_rules_caching_static_HTML_with_drupal.png) - -Now, when Cloudflare is serving cached files, a response header `Cf-Cache-Status: HIT` will be sent back to the browser. - -*** - -## Related Resources - -* [Caching Cloudflare CDN](/cache/concepts/default-cache-behavior/) diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/caching-static-html-with-wordpresswoocommerce.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/caching-static-html-with-wordpresswoocommerce.mdx deleted file mode 100644 index 748faafefe1d73..00000000000000 --- a/src/content/docs/support/third-party-software/content-management-system-cms/caching-static-html-with-wordpresswoocommerce.mdx +++ /dev/null @@ -1,63 +0,0 @@ ---- -pcx_content_type: troubleshooting -source: https://support.cloudflare.com/hc/en-us/articles/236166048-Caching-Static-HTML-with-WordPress-WooCommerce -title: Caching Static HTML with WordPress/WooCommerce - ---- - -import { DashButton } from "~/components"; - -## Overview - -:::note - -Customers in all Cloudflare plans can configure caching HTML files. However, Business and Enterprise customers can bypass HTML caching when a cookie is sent with a request *Bypass Cache on Cookie* setting using Cloudflare Page Rules. -::: - -This allows for static HTML to be cached at our edge, with no need for it to be regenerated from request to request.  - -Enterprise Cloudflare customers can use *Custom Cache Keys* to take their performance further, contact your Customer Success Manager for more details. - -*** - -## Prerequisites - -Before starting - be sure that Cloudflare is set to respect `Cache-Control` headers from your origin web server; otherwise, you may find `Cache-Control` headers are overridden by Cloudflare with the value set in the **Browser Cache TTL** option. To set the **Respect Existing Headers** option: - -1. In the Cloudflare dashboard, go to the **Caching** page. - - - -2. Under **Browser Cache TTL**, select the **Respect Existing Headers** value. - -*** - -## Cache Static HTML with Cloudflare Cache Rules - -1. In the Cloudflare dashboard, go to the **Caching** page. - - - -2. Select **Create rule**. -3. Set the cache rule to match your WordPress installation path. If your site is at [https://www.example.com](https://www.example.com), the rule would be [https://www.example.com](https://www.example.com/). -4. Select the appropriate settings to cache static HTML: - -* *Eligible for cache* instructs Cloudflare to cache static HTML. -* When the *Bypass Cache on Cookie* rule matches the criteria you set, Cloudflare won't cache HTML ([though static images and other files will still be cached](/cache/concepts/default-cache-behavior/)). Depending on whether you're using raw WordPress, or WooCommerce, you should use one of the configurations below: - -:::caution - - -| WordPress type | Cookie configuration | -| -------------------------- | ---------------------------------------------------- | -| WordPress (native) | wp-.\*\|wordpress.\*\|comment\_.\* | -| WordPress with WooCommerce | wp-.\*\|wordpress.\*\|comment\_.\*\|woocommerce\_.\* | - - -::: - -* Finally, setting *Edge Cache TTL* will define the maximum period of time Cloudflare should keep cached files before getting them back from the origin web server. Even after setting a long Edge Cache TTL time, you can still [manually clear the cache](https://support.cloudflare.com/hc/en-us/articles/200169246-How-do-I-purge-my-cache-) or use our WordPress plugin to automatically manage cache purging. - -5. Select **Save and Deploy**. - -Additionally, by using the [*Automatic Cache Management* feature of the Cloudflare WordPress plugin](https://support.cloudflare.com/hc/en-us/articles/115002708027-What-does-Automatic-Cache-Management-in-the-Cloudflare-Plugin-do-), you are able to automatically purge the cache for your site after your site changes (i.e. changing/customizing your theme or editing, deleting or creating a post, attachment or page). diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/can-i-use-wordpress-caching-plugins-like-super-cache-or-w3-total-cache-w3tc-with-cloudflare.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/can-i-use-wordpress-caching-plugins-like-super-cache-or-w3-total-cache-w3tc-with-cloudflare.mdx deleted file mode 100644 index fac5a80b5350b3..00000000000000 --- a/src/content/docs/support/third-party-software/content-management-system-cms/can-i-use-wordpress-caching-plugins-like-super-cache-or-w3-total-cache-w3tc-with-cloudflare.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -pcx_content_type: troubleshooting -source: https://support.cloudflare.com/hc/en-us/articles/200169756-Can-I-use-WordPress-caching-plugins-like-Super-Cache-or-W3-Total-Cache-W3TC-with-Cloudflare- -title: Can I use WordPress caching plugins like Super Cache or W3 Total Cache - (W3TC) with Cloudflare - ---- - -## Overview - -It is possible to cache the HTML of a WordPress site at Cloudflare's Edge using a feature known as "Bypass Cache on Cookie". This can dramatically improve the speed of your website and reduce server load; in cases where the HTML is cached, Cloudflare will not need to make a roundtrip to your web server. In order to utilize this feature, refer to the article: [Caching Static HTML with WordPress/WooCommerce](https://support.cloudflare.com/hc/en-us/articles/236166048-Caching-Static-HTML-with-WordPress-WooCommerce). - -Cloudflare is able to proxy HTTP traffic of any website, including WordPress sites with third-party performance plugins installed, however, please note that these plugins are installed at your own risk. diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-and-joomla-recommended-first-steps.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-and-joomla-recommended-first-steps.mdx deleted file mode 100644 index abc44491809c3c..00000000000000 --- a/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-and-joomla-recommended-first-steps.mdx +++ /dev/null @@ -1,62 +0,0 @@ ---- -pcx_content_type: troubleshooting -source: https://support.cloudflare.com/hc/en-us/articles/201997250-Cloudflare-and-Joomla-Recommended-First-Steps -title: Cloudflare and Joomla Recommended First Steps ---- - -## Overview - -These basic steps will help reduce common areas of confusion for Joomla users that are new to the Cloudflare services. In addition, these steps are very quick and will generally take you only a few minutes of your time to help you make your experience using Cloudflare better. - ---- - -## Restore visitor IP - -Restore visitor IP by following the directions in [this article](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/). Since Cloudflare acts as a proxy for sites using our network, Cloudflare's IPs are going to show in your logs, including comments, unless you install something to restore the original visitor IP. - -Why should you restore visitor IP? - -If you receive a lot of comments or spam on your blog, you may mistakenly believe that Cloudflare is spamming you. Some other Joomla plugins or extensions may also rely on the original visitor IP for the services to work properly and reduce false alerts. - -:::note -You don't need to worry about this if you activated through a hosting partner, since they already restore visitor IP addresses on their servers by default. -::: - ---- - -## Create a Page Rule to exclude Joomla - -Create a [Page Rule](/rules/page-rules/) to exclude the Joomla admin or Joomla login sections from Cloudflare's caching and performance features. - -Why do this? - -While there is not always an issue, we have seen instances where optional performance features like Rocket Loader may inadvertently break certain functions (editors, etc.) in your Joomla back end. - ---- - -## Skip security features for specific IP addresses - -You can use WAF custom rules to [skip certain security features](/waf/custom-rules/skip/) for IP addresses you want traffic from or expect traffic from. Some common services you probably want to allow include: - -- APIs you are getting data from -- Monitoring services you use to monitor your site's uptime -- Security services -- IP addresses you frequently log in from - -Why do this? - -If you have enabled and configured [Cloudflare's Web Application Firewall](/waf/), legitimate services and/or you may get challenged while accessing your backend. To prevent issues on your site, consider skipping certain security features for requests coming from known IP addresses. - -:::note -Cloudflare allows known search engine and social media crawlers. If you decide to block specific countries, you must use care because you may end up inadvertently blocking their crawlers (blocking the USA, for example, could mean that their crawler gets challenged). -::: - ---- - -## Ensure requests from Cloudflare's IP ranges aren't blocked or limited - -If you are using services like `.htaccess`, firewalls or server mods to manage access to your site from visitors, you must ensure that requests from [Cloudflare's IP ranges](https://www.cloudflare.com/ips/) are not being blocked or limited in any way. The number one cause of "site offline" issues in Cloudflare's support channel is something blocking or restricting requests from Cloudflare IPs. To prevent this, ensure that all of Cloudflare's IPs are allowed on your server. - -Why do this? - -Prevent false offline messages from appearing on your site to you or visitors. diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx index b92283107eeb36..3c7f952c21eccc 100644 --- a/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx +++ b/src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx @@ -20,13 +20,6 @@ Automatic Cache Management uses native hooks built into WordPress. The Cloudflar * switch\_theme * customize\_save\_after -:::note - -This feature works great [when caching HTML on -WordPress](/support/third-party-software/content-management-system-cms/caching-static-html-with-wordpresswoocommerce/) with -the Bypass Cache on Cookie setting. -::: - *** ## Enable Automatic Cache Management diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/speed-up-wordpress-and-improve-performance.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/speed-up-wordpress-and-improve-performance.mdx index 46d8395a0cf2cf..56c2150e3a0462 100644 --- a/src/content/docs/support/third-party-software/content-management-system-cms/speed-up-wordpress-and-improve-performance.mdx +++ b/src/content/docs/support/third-party-software/content-management-system-cms/speed-up-wordpress-and-improve-performance.mdx @@ -13,14 +13,6 @@ Cloudflare's CDN services can help cache your content across our giant global n Cloudflare's "[Bypass Cache on Cookie](/cache/how-to/cache-rules/examples/bypass-cache-on-cookie/)" functionality allows non-logged-in pages to be fully cached by Cloudflare. This means your server can save time and resources by not having to regenerate pages where the HTML is effectively static, whilst not interfering with dynamic behaviour - as soon as a user logs-in to the WordPress dashboard or adds something to their WooCommerce, the Edge cache is bypassed. -:::note - -This feature is available to Business and Enterprise users. Instructions -on configuring this can be found in the article: [Caching Static HTML -with -WordPress/WooCommerce](/support/third-party-software/content-management-system-cms/caching-static-html-with-wordpresswoocommerce/). -::: - ### Optimise Images Images can be incredibly costly to page load times; fortunately, Cloudflare can dramatically help improve image load times. You can find these features in the Cloudflare dashboard by going to **Speed** > **Optimization** > **Image Optimization**. diff --git a/src/content/docs/support/third-party-software/content-management-system-cms/using-cloudflare-and-drupal-five-easy-recommended-steps.mdx b/src/content/docs/support/third-party-software/content-management-system-cms/using-cloudflare-and-drupal-five-easy-recommended-steps.mdx deleted file mode 100644 index 0c32a87d922a9b..00000000000000 --- a/src/content/docs/support/third-party-software/content-management-system-cms/using-cloudflare-and-drupal-five-easy-recommended-steps.mdx +++ /dev/null @@ -1,52 +0,0 @@ ---- -pcx_content_type: troubleshooting -source: https://support.cloudflare.com/hc/en-us/articles/201883834-Using-Cloudflare-and-Drupal-Five-Easy-Recommended-Steps -title: Using Cloudflare and Drupal Five Easy Recommended Steps ---- - -## Overview - -These basic steps will help reduce common areas of confusion for Drupal users that are new to using Cloudflare to speed up and protect their sites. In addition, these steps are very quick and will generally take only a few minutes of your time to go through. - -**Step #1** - -Install the [Cloudflare Drupal plugin](https://drupal.org/project/cloudflare) to restore visitor IP information. Since Cloudflare acts as a proxy for sites using our network, Cloudflare’s IPs are going to show in your logs, including comments, unless you install something to restore the original visitor IP. - -Why should you install the plugin? - -If you receive a lot of comments or spam on your blog, you may mistakenly believe that Cloudflare is spamming you. Some other Drupal plugins or extensions may also rely on the original visitor IP for the services to work properly and reduce false alerts. - -Note: You don’t need to worry about this if you activated through a certified Cloudflare [certified Cloudflare Hosting partner](https://www.cloudflare.com/partners/technology-partners/), since they already [restore visitor IPs](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/) by default. - -**Step #2** - -Create a [Page Rule](/rules/page-rules/) to exclude the Drupal admin or Drupal login sections from Cloudflare’s caching and performance features. You can access Page Rules in **Rules** > **Page Rules**. - -Why do this? - -While there is not always an issue, we have seen some optional performance features like Rocket Loader inadvertently breaking certain functions (editors, etc.) in your site's admin area. - -**Step #3** - -[Skip some security features](/waf/custom-rules/skip/) for specific IP addresses you expect traffic from. Some common services you probably want to allow include: - -- APIs you are getting data from -- Monitoring services you use to monitor your site's uptime -- Security services -- IP addresses you frequently log in from - -Why do this? - -If you have enabled and configured [Cloudflare's Web Application Firewall](/waf/), legitimate services and/or you may get challenged while accessing your backend. To prevent issues on your site, consider skipping certain security features for requests coming from known IP addresses. - -**Note:** Cloudflare allows known search engine and social media crawlers. If you decide to block specific countries, you must use care because you may end up inadvertently blocking their crawlers (blocking the USA, for example, could mean that their crawler gets challenged). - -**Step #4** - -If you are using services like `.htaccess`, firewalls, or server mods to manage access to your site from visitors, it is vitally important to make sure requests from [Cloudflare's IP ranges](https://www.cloudflare.com/ips) are not being blocked or limited in any way. The number one cause of site offline issues in our support channel is something blocking or restricting requests from our IPs, so please take the time to make sure that all of Cloudflare's IPs are allowed on your server and with your hosting provider. - -Why do this? - -Prevent false offline messages from appearing on your site to you or visitors. - -**Note:** You do not need to ask your host to allow our IPs when activating through a hosting partner. You should still make sure any other security services you're running on the site have our IPs allowed. diff --git a/src/content/docs/support/third-party-software/e-commerce/caching-static-html-with-magento-business-and-enterprise-only.mdx b/src/content/docs/support/third-party-software/e-commerce/caching-static-html-with-magento-business-and-enterprise-only.mdx deleted file mode 100644 index 20e82823e8c59f..00000000000000 --- a/src/content/docs/support/third-party-software/e-commerce/caching-static-html-with-magento-business-and-enterprise-only.mdx +++ /dev/null @@ -1,89 +0,0 @@ ---- -pcx_content_type: troubleshooting -source: https://support.cloudflare.com/hc/en-us/articles/236168808-Caching-Static-HTML-with-Magento-Business-and-Enterprise-only- -title: Caching Static HTML with Magento (Business and Enterprise only) - ---- - -import { DashButton } from "~/components"; - -## Overview - -:::note - -All Cloudflare customers can configure caching HTML files. However, only customers in the Business and Enterprise plans are able to bypass HTML caching when a cookie is sent with Bypass Cache on Cookie request using Cloudflare Page Rules. -::: - -Business and Enterprise customers using Magento can cache anonymous page views with our *Bypass Cache on Cookie* page rule. This setting caches static HTML at the Cloudflare edge with no need for regeneration from request to request. - -Before logging in to the Magento admin panel or adding something to a shopping cart, the page view is anonymized and it's possible to cache the requests so that Magento doesn't need to constantly regenerate the HTML at your origin server. - -*** - -## Cache Static HTML with Cloudflare Page Rules - -To cache static HTML using Cloudflare Page Rules: - -1. In the Cloudflare dashboard, go to the **Caching** page. - - - -2. Under **Browser Cache TTL**, choose **Respect Existing Headers**. - -With this setting in place, you can set the necessary Page Rules to cache anonymize page visits. - -3. In the Cloudflare dashboard, go to the **Rules** page. - - - -4. Select **Create Page Rule** and enter your domain. In the example below, the domain is `www.orangeclouded.com`. - -* *Cache Everything* will instruct Cloudflare to cache static HTML. -* When the *Bypass Cache on Cookie* rule matches the criteria we set, Cloudflare won't cache HTML ([though static images and other files will still be cached](/cache/concepts/default-cache-behavior/)). Depending on whether you're using Magento 1 or Magento 2, you will need a different rule: - -`Magento 1    external_no_cache=.*|PHPSESSID=.*|adminhtml=.* Magento 2    admin=.*|PHPSESSID=.*|private_content_version=.*` - -* Finally, setting *Edge Cache TTL* will define the maximum period of time Cloudflare should keep cached files before getting them back from the origin. Even after setting a long Edge Cache TTL time, you can still  before this time expires. - -![The Create a Page Rule dialog with settings to instruct Cloudflare to cache static HTML, the Bypass Cache on cookie rule instructing Cloudflare not to cache HTML while static images and other files are still cached, and the Edge Cache TTL set to a month.](~/assets/images/support/hc-import-page_rules_caching_static_html_with_magento.png) - -5. Select **Save and Deploy**. - -:::note - -Enterprise Cloudflare customers can use Custom Cache Keys to take their -performance further, contact your Customer Success Manager if -interested. -::: - -*** - -## Troubleshooting issues on Magento 1.8.x or 1.9.x - -If you setup **Bypass Cache on Cookie** on a Magento 1.8.x site or a 1.9.x site you may notice that the "Add to Cart" functionality doesn't work on a user's first attempt to add an item to a shopping cart. - -Magento 1.8.x and 1.9.x introduced [Cross Site Request Forgery checks](https://www.section.io/blog/csrf-and-caching/) (CSRF) across all Magento forms. As this uses cookies, anonymous caching mechanisms can cause issues. There are three ways to fix this issue. We have listed the options based on their security level below. - -1. Least Secure: The configuration at *System -> Configuration -> System -> CSRF protection -> Add Secret Key To Url* is set to *Yes* by default. Setting this to *No* will disable CSRF security protection on your entire Magento frontend, you should only use this option if you have a separate mechanism for CSRF protection enabled on your site, we do not recommend this approach. Please note that there is a similarly named configuration for the admin panel at *System -> ADMIN -> System -> CSRF protection -> Add Secret Key To Url*; this configuration should be kept to Yes and **not altered**. This configuration provides security to your admin endpoint and therefore extra caution should be used. - -2. Somewhat Secure: A Magento community module exists which allows users to only disable CSRF checks on the "Add to Cart" form, where the security risk is less significant; the [Inovarti\_FixAddToCartMage18](https://github.com/deivisonarthur/Inovarti_FixAddToCartMage18/blob/master/README.md) plugin does this by allowing the "Add to Cart" functionality from CSRF protection.  - -3. Most Secure: The best alternative is to use AJAX to dynamically fill in the value of the CSRF token in your Magento site. When a user clicks the button to add something to their cart, some JavaScript jumps in to update the CSRF token in the forms to match the user’s session. This can enable most of the page to be served from cache but will still require a request back to the origin to fetch the token. - -This final AJAX mechanism is implemented in a plugin called the [Magento Turpentine extension](https://github.com/nexcess/magento-turpentine). Whilst this plugin was built for performing caching with Varnish, it can also be used with Cloudflare. - -There are a couple of options for installing this: - -* Download and install the tarball package from the Downloads page on GitHub (note that this is not the "Download as tar.gz" button) and install through Magento Connect Downloader or Magento's *mage* command. -* Install through  with the extension key: `http://connect20.magentocommerce.com/community/Nexcessnet_Turpentine` -* Install with . You would just need to use: `modman clone https://github.com/nexcess/magento-turpentine.git` - -After installing the plugin, navigate to *System -> Configuration -> TURPENTINE -> Varnish Options* and find the "Use VCL fix" option, set it to "Disable" and save. - -![Use VCL fix option set to Disable.](~/assets/images/support/hc-import-use_vcl_fix_magento_cache_static_html.png) - -*** - -## Related resources - -* [Understanding Cloudflare's CDN](/cache/concepts/default-cache-behavior/) diff --git a/src/content/docs/support/third-party-software/e-commerce/index.mdx b/src/content/docs/support/third-party-software/e-commerce/index.mdx deleted file mode 100644 index ea1742a11a972f..00000000000000 --- a/src/content/docs/support/third-party-software/e-commerce/index.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -pcx_content_type: navigation -title: e-Commerce -sidebar: - order: 2 - ---- - -import { DirectoryListing } from "~/components" - -Below you will find links to the relevant sections for e-Commerce support-focused material. - -