Skip to content

Commit f58edae

Browse files
authored
[Support] Update Support KB links (#25441)
1 parent 9ba43b9 commit f58edae

File tree

7 files changed

+11
-9
lines changed

7 files changed

+11
-9
lines changed

src/content/docs/support/customer-incident-management-policy.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -226,7 +226,7 @@ Lower priority (P2 and P3) tickets may be categorized using labels and nomenclat
226226

227227
### Security and Privacy Incidents
228228

229-
It is critical to understand that incidents that are classified under the categories of Security and Privacy require special handling and procedures. Customers should report these incidents directly to Cloudflare by [Contacting Cloudflare Support](https://support.cloudflare.com/hc/en-us/articles/200172476-Contacting-Cloudflare-Support), who will follow specified incident procedures as defined by the Cloudflare Security & Privacy teams.
229+
It is critical to understand that incidents that are classified under the categories of Security and Privacy require special handling and procedures. Customers should report these incidents directly to Cloudflare by [Contacting Cloudflare Support](/support/contacting-cloudflare-support/), who will follow specified incident procedures as defined by the Cloudflare Security & Privacy teams.
230230

231231
### High Severity / Priority Incidents
232232

src/content/docs/support/third-party-software/content-management-system-cms/cloudflare-wordpress-plugin-automatic-cache-management.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Automatic Cache Management uses native hooks built into WordPress. The Cloudflar
2424

2525
## Enable Automatic Cache Management
2626

27-
To enable Automatic Cache Management after [installing the WordPress plugin](https://support.cloudflare.com/hc/en-us/articles/227634427-Using-Cloudflare-with-WordPress),
27+
To enable Automatic Cache Management after [installing the WordPress plugin](/automatic-platform-optimization/):
2828

2929
1. Log in to your WordPress account.
3030
2. Click **Settings** and choose the Cloudflare plugin. The Cloudflare plugin home page appears.

src/content/docs/support/third-party-software/content-management-system-cms/how-do-i-enable-http2-server-push-in-wordpress.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ HTTP/2 Server Push allows a website to push content to a browser, without having
1111
Article IDs: 115002816808 | How do I enable HTTP/2 Server Push in WordPress
1212
](~/assets/images/support/hc-import-http2_server_push_2.png)
1313

14-
Cloudflare supports HTTP/2 Server Push and it can be enabled for stylesheets and scripts using Cloudflare’s WordPress plugin. In order to utilise this feature, you must first ensure you have the Cloudflare WordPress plugin [installed and set-up on your site](https://support.cloudflare.com/hc/en-us/articles/227634427-Using-Cloudflare-with-WordPress).
14+
Cloudflare supports HTTP/2 Server Push and it can be enabled for stylesheets and scripts using Cloudflare’s WordPress plugin. In order to utilise this feature, you must first ensure you have the Cloudflare WordPress plugin [installed and set up on your site](/automatic-platform-optimization/).
1515

1616
Once the plugin is installed, you can enable HTTP/2 Server Push by adding the following line to your `wp-config.php` file:
1717

src/content/docs/support/third-party-software/content-management-system-cms/wordpress.com-and-cloudflare.mdx

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,10 @@ title: WordPress.com and Cloudflare
88

99
Cloudflare and WordPress.com are partnering to offer customers Cloudflare's performance and security solutions with WordPress.com's web-hosting platform. Getting started is easy.
1010

11-
1\. Add your WordPress site to Cloudflare. Visit [Creating a Cloudflare account and adding a website](https://support.cloudflare.com/hc/en-us/articles/201720164) for more information.
11+
1\. Add your WordPress site to Cloudflare. Do the following:
12+
13+
- [Create a Cloudflare account](/fundamentals/account/create-account/).
14+
- [Onboard your domain](/fundamentals/manage-domains/add-site/) to Cloudflare.
1215

1316
During this process, Cloudflare scans your existing WordPress.com DNS records and displays them. The records will look similar to the examples below.
1417

@@ -65,7 +68,7 @@ WordPress.com automatically adds the javascript to each page of your site. You c
6568

6669
## **Automatic Platform Optimization for WordPress.com ($5/month, included with Pro and Business plans)**
6770

68-
Cloudflare's [Automatic Platform Optimization](https://www.cloudflare.com/automatic-platform-optimization/wordpress/) for WordPress.com is the easiest way to drastically speed up your WordPress.com site. With the [APO plugin](https://wordpress.org/plugins/cloudflare/), Cloudflare accelerates your WordPress.com site by intelligently caching dynamic content, which means fast performance for your visitors no matter where they are. Find out more from our [blog](https://blog.cloudflare.com/automatic-platform-optimizations-starting-with-wordpress/) and [support article](https://support.cloudflare.com/hc/en-us/articles/360049822312-Understanding-Automatic-Platform-Optimization-APO-with-WordPress).
71+
Cloudflare's [Automatic Platform Optimization](https://www.cloudflare.com/automatic-platform-optimization/wordpress/) for WordPress.com is the easiest way to drastically speed up your WordPress.com site. With the [APO plugin](https://wordpress.org/plugins/cloudflare/), Cloudflare accelerates your WordPress.com site by intelligently caching dynamic content, which means fast performance for your visitors no matter where they are. For more information, refer to [Automatic Platform Optimization](/automatic-platform-optimization/) and to the [blog](https://blog.cloudflare.com/automatic-platform-optimizations-starting-with-wordpress/).
6972

7073
### **Requirements**
7174

src/content/docs/support/third-party-software/others/configure-cloudflare-and-heroku-over-https.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ import { Example, DashButton } from "~/components";
1010

1111
Heroku is a cloud PaaS that supports several pre-configured programming languages. Heroku deals with all your infrastructure so you can focus on your application without having to work at the command line.
1212

13-
This article describes how to configure Heroku with Cloudflare to serve your traffic over HTTPS. For this article, we'll assume that you already have an [active domain on Cloudflare](https://support.cloudflare.com/hc/en-us/sections/200820158-CloudFlare-101), as well as a running Heroku app.
13+
This article describes how to configure Heroku with Cloudflare to serve your traffic over HTTPS. For this article, we'll assume that you already have an [active domain on Cloudflare](/fundamentals/manage-domains/), as well as a running Heroku app.
1414

1515
---
1616

src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ title: Restoring original visitor IPs
66

77
import { Render } from "~/components";
88

9-
When your [website traffic is routed through the Cloudflare network](https://support.cloudflare.com/hc/articles/205177068), we act as a reverse proxy. This allows Cloudflare to speed up page load time by routing packets more efficiently and caching static resources (images, JavaScript, CSS, etc.). As a result, when responding to requests and logging them, your origin server returns a [Cloudflare IP address](https://www.cloudflare.com/ips/).
9+
When your [website traffic is routed through the Cloudflare network](/fundamentals/concepts/how-cloudflare-works/), we act as a reverse proxy. This allows Cloudflare to speed up page load time by routing packets more efficiently and caching static resources (images, JavaScript, CSS, etc.). As a result, when responding to requests and logging them, your origin server returns a [Cloudflare IP address](https://www.cloudflare.com/ips/).
1010

1111
For example, if you install applications that depend on the incoming IP address of the original visitor, a Cloudflare IP address is logged by default. The original visitor IP address appears in an appended HTTP header called [`CF-Connecting-IP`](/fundamentals/reference/http-headers/). By following our [web server instructions](#web-server-instructions), you can log the original visitor IP address at your origin server. If this HTTP header is not available when requests reach your origin server, check your [Transform Rules](/rules/transform/) and [Managed Transforms](/rules/transform/managed-transforms/) configuration.
1212

src/content/docs/workers/testing/miniflare/core/fetch.mdx

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,8 +59,7 @@ console.log(await res.json()); // { url: "http://localhost:8787/2", header: "2"
5959
```
6060

6161
When dispatching events, you are responsible for adding
62-
[`CF-*` headers](https://support.cloudflare.com/hc/en-us/articles/200170986-How-does-Cloudflare-handle-HTTP-Request-headers-)
63-
and the
62+
[`CF-*` headers](/fundamentals/reference/http-headers/) and the
6463
[`cf` object](/workers/runtime-apis/request#incomingrequestcfproperties).
6564
This lets you control their values for testing:
6665

0 commit comments

Comments
 (0)