diff --git a/src/assets/images/rules/normalization/url-normalization-settings.png b/src/assets/images/rules/normalization/url-normalization-settings.png index 2c9d3df5f96c3e..2b26b21a79595c 100644 Binary files a/src/assets/images/rules/normalization/url-normalization-settings.png and b/src/assets/images/rules/normalization/url-normalization-settings.png differ diff --git a/src/content/docs/firewall/troubleshooting/required-changes-to-enable-url-normalization.mdx b/src/content/docs/firewall/troubleshooting/required-changes-to-enable-url-normalization.mdx index 4a26910c44ee92..2936c3e2d16f8b 100644 --- a/src/content/docs/firewall/troubleshooting/required-changes-to-enable-url-normalization.mdx +++ b/src/content/docs/firewall/troubleshooting/required-changes-to-enable-url-normalization.mdx @@ -2,36 +2,35 @@ pcx_content_type: troubleshooting source: https://support.cloudflare.com/hc/en-us/articles/360057896851-Required-Firewall-Rule-changes-to-enable-URL-normalization title: Required firewall rule changes to enable URL normalization - --- -import { Render } from "~/components" +import { Render } from "~/components"; On 2021-04-08, Cloudflare announced [URL normalization](/rules/normalization/), a feature that protects zones by normalizing HTTP request URI paths. -Malicious users can craft specific URIs that could be interpreted differently by firewall systems and origin systems. When you enable **Normalize incoming URLs**, all rules filtering on the URI path will receive the URL in a canonical form, which provides an extra layer of protection against these malicious users.  +Malicious users can craft specific URIs that could be interpreted differently by firewall systems and origin systems. When you enable **Normalize incoming URLs**, all rules filtering on the URI path will receive the URL in a canonical form, which provides an extra layer of protection against these malicious users. -Cloudflare gradually enabled URL normalization for all Cloudflare zones except for those that could be impacted by this change. We determined the impacted zones by analyzing all firewall rules, looking for patterns in HTTP fields that would no longer match when using URL normalization techniques. +Cloudflare gradually enabled URL normalization for all Cloudflare zones except for those that could be impacted by this change. We determined the impacted zones by analyzing all firewall rules, looking for patterns in HTTP fields that would no longer match when using URL normalization techniques. These fields are the following: -* `http.request.uri.path` -* `http.request.full_uri` -* `http.request.uri` +- `http.request.uri.path` +- `http.request.full_uri` +- `http.request.uri` Cloudflare did not enable URL normalization automatically for zones that would be impacted by these changes to prevent any change in behavior of your existing firewall rules. ## Why URL normalization is important -Cloudflare strongly recommends that you enable **Normalize incoming URLs** in **Rules** > **Settings** to strengthen your zone's security posture. Not doing so leaves your zone at greater risk of a successful attack. Malicious parties could craft the URL in a way that the rules are not accounting for. +Cloudflare strongly recommends that you enable **Normalize incoming URLs** in **Rules** > **URL Normalization** to strengthen your zone's security posture. Not doing so leaves your zone at greater risk of a successful attack. Malicious parties could craft the URL in a way that the rules are not accounting for. For example, a firewall rule with an expression such as `http.request.uri.path contains "/login"` could be bypassed if the malicious actor has encoded the `l` character as `%6C`. In this scenario, and with URL normalization disabled, traffic would not be matched by the firewall rule. Refer to [How URL normalization works](/rules/normalization/how-it-works/) for more information and additional examples. -*** +--- ## Recommended procedure @@ -46,23 +45,23 @@ These steps will ensure a stronger security posture on your zone(s). Before enabling URL normalization, you should review the affected firewall rules on your zone(s) and take one of the following approaches: -* Edit these firewall rules to remove the parts which will no longer trigger once normalized — for example, any rules that look for `//` or `../` in URL paths. Administrators previously created these rules to perform a limited URL normalization, and these rules can now be safely disabled and then deleted. +- Edit these firewall rules to remove the parts which will no longer trigger once normalized — for example, any rules that look for `//` or `../` in URL paths. Administrators previously created these rules to perform a limited URL normalization, and these rules can now be safely disabled and then deleted. -* If you wish to identify visitors with non-normalized URI paths with these firewall rules, you should update them to use the original (or raw) non-normalized fields. These fields are the following: +- If you wish to identify visitors with non-normalized URI paths with these firewall rules, you should update them to use the original (or raw) non-normalized fields. These fields are the following: - * `raw.http.request.uri.path` - * `raw.http.request.full_uri` - * `raw.http.request.uri` + - `raw.http.request.uri.path` + - `raw.http.request.full_uri` + - `raw.http.request.uri` ### 2. Enable URL normalization -Once you have updated the affected firewall rules, enable URL normalization in **Rules** > **Settings**. +Once you have updated the affected firewall rules, enable URL normalization in **Rules** > **URL Normalization**. A Cloudflare user must have the [Firewall role](/fundamentals/setup/manage-members/roles/) or one of the Administrator roles to access URL normalization settings in the dashboard. -*** +--- ## Related resources -* [URL normalization](/rules/normalization/) -* [Transform Rules](/rules/transform/) +- [URL normalization](/rules/normalization/) +- [Transform Rules](/rules/transform/) diff --git a/src/content/docs/rules/normalization/examples.mdx b/src/content/docs/rules/normalization/examples.mdx index 936a618d75b310..38d19857a52247 100644 --- a/src/content/docs/rules/normalization/examples.mdx +++ b/src/content/docs/rules/normalization/examples.mdx @@ -1,36 +1,31 @@ --- -title: Examples +title: URL normalization examples pcx_content_type: configuration sidebar: order: 6 -head: - - tag: title - content: URL normalization examples + label: Examples description: Examples of the impact of different URL normalization settings in the URLs of incoming requests. - +tableOfContents: false --- The following table shows how different [URL normalization settings](/rules/normalization/settings/) affect request URLs before they pass to other Cloudflare features and to the origin server: - - | Incoming URL | Normalization type | Normalize incoming URLs | Normalize URLs to origin | URL at Cloudflare's network | URL passed to origin server | | ---------------------------- | ------------------ | ----------------------- | ------------------------ | ------------------------------ | ------------------------------ | -| `www.example.com/hello` | (any) | *Off* | *Off* | `www.example.com/hello` | `www.example.com/hello` | -| `www.example.com/hello` | (any) | *On* | *Off* | `www.example.com/hello` | `www.example.com/hello` | -| `www.example.com/hello` | (any) | *On* | *On* | `www.example.com/hello` | `www.example.com/hello` | -| `example.com/%68ello` | (any) | *Off* | *Off* | `example.com/%68ello` | `example.com/%68ello` | -| `example.com/%68ello` | (any) | *On* | *Off* | `example.com/hello` | `example.com/%68ello` | -| `example.com/%68ello` | (any) | *On* | *On* | `example.com/hello` | `example.com/hello` | -| `example.com/%68ello//pa\th` | *RFC-3986* | *Off* | *Off* | `example.com/%68ello//pa\th` | `example.com/%68ello//pa\th` | -| `example.com/%68ello//pa\th` | *RFC-3986* | *On* | *Off* | `example.com/hello//pa%5Cth` | `example.com/%68ello//pa\th` | -| `example.com/%68ello//pa\th` | *RFC-3986* | *On* | *On* | `example.com/hello//pa%5Cth` | `example.com/hello//pa%5Cth` | -| `example.com/%68ello//pa\th` | *Cloudflare* | *Off* | *Off* | `example.com/%68ello//pa\th` | `example.com/%68ello//pa\th` | -| `example.com/%68ello//pa\th` | *Cloudflare* | *On* | *Off* | `example.com/hello/pa/th` | `example.com/%68ello//pa\th` | -| `example.com/%68ello//pa\th` | *Cloudflare* | *On* | *On* | `example.com/hello/pa/th` | `example.com/hello/pa/th` | -| `example.com/hello//../path` | *RFC-3986* | *On* | *On* | `example.com/hello/path` | `example.com/hello/path` | -| `example.com/hello//../path` | *Cloudflare* | *On* | *On* | `example.com/path` | `example.com/path` | -| `example.com/hello/\../path` | *RFC-3986* | *On* | *On* | `example.com/hello/%5C../path` | `example.com/hello/%5C../path` | -| `example.com/hello/\../path` | *Cloudflare* | *On* | *On* | `example.com/path` | `example.com/path` | - +| `www.example.com/hello` | (any) | _Off_ | _Off_ | `www.example.com/hello` | `www.example.com/hello` | +| `www.example.com/hello` | (any) | _On_ | _Off_ | `www.example.com/hello` | `www.example.com/hello` | +| `www.example.com/hello` | (any) | _On_ | _On_ | `www.example.com/hello` | `www.example.com/hello` | +| `example.com/%68ello` | (any) | _Off_ | _Off_ | `example.com/%68ello` | `example.com/%68ello` | +| `example.com/%68ello` | (any) | _On_ | _Off_ | `example.com/hello` | `example.com/%68ello` | +| `example.com/%68ello` | (any) | _On_ | _On_ | `example.com/hello` | `example.com/hello` | +| `example.com/%68ello//pa\th` | _RFC-3986_ | _Off_ | _Off_ | `example.com/%68ello//pa\th` | `example.com/%68ello//pa\th` | +| `example.com/%68ello//pa\th` | _RFC-3986_ | _On_ | _Off_ | `example.com/hello//pa%5Cth` | `example.com/%68ello//pa\th` | +| `example.com/%68ello//pa\th` | _RFC-3986_ | _On_ | _On_ | `example.com/hello//pa%5Cth` | `example.com/hello//pa%5Cth` | +| `example.com/%68ello//pa\th` | _Cloudflare_ | _Off_ | _Off_ | `example.com/%68ello//pa\th` | `example.com/%68ello//pa\th` | +| `example.com/%68ello//pa\th` | _Cloudflare_ | _On_ | _Off_ | `example.com/hello/pa/th` | `example.com/%68ello//pa\th` | +| `example.com/%68ello//pa\th` | _Cloudflare_ | _On_ | _On_ | `example.com/hello/pa/th` | `example.com/hello/pa/th` | +| `example.com/hello//../path` | _RFC-3986_ | _On_ | _On_ | `example.com/hello/path` | `example.com/hello/path` | +| `example.com/hello//../path` | _Cloudflare_ | _On_ | _On_ | `example.com/path` | `example.com/path` | +| `example.com/hello/\../path` | _RFC-3986_ | _On_ | _On_ | `example.com/hello/%5C../path` | `example.com/hello/%5C../path` | +| `example.com/hello/\../path` | _Cloudflare_ | _On_ | _On_ | `example.com/path` | `example.com/path` | diff --git a/src/content/docs/rules/normalization/how-it-works.mdx b/src/content/docs/rules/normalization/how-it-works.mdx index 38761fc471c901..5958856bb932ad 100644 --- a/src/content/docs/rules/normalization/how-it-works.mdx +++ b/src/content/docs/rules/normalization/how-it-works.mdx @@ -1,12 +1,9 @@ --- -title: How it works +title: How URL normalization works pcx_content_type: concept sidebar: order: 3 -head: - - tag: title - content: How URL normalization works - + label: How it works --- URL normalization modifies separators, encoded elements, and literal bytes in incoming URLs so that they conform to a consistent formatting standard. @@ -15,8 +12,8 @@ For example, consider a WAF custom rule that blocks requests whose URLs match `w The two available types of URL normalization are: -* [RFC 3986 normalization](#rfc-3986-normalization) -* [Cloudflare normalization](#cloudflare-normalization) +- [RFC 3986 normalization](#rfc-3986-normalization) +- [Cloudflare normalization](#cloudflare-normalization) The location where URL normalization will occur depends on the [configured settings](/rules/normalization/settings/). @@ -26,14 +23,14 @@ For examples of the different settings and their impact on request URLs, refer t The URL normalization performed according to [RFC 3986](https://www.ietf.org/rfc/rfc3986.txt) is as follows: -* The following unreserved characters are [percent decoded](https://tools.ietf.org/html/rfc3986#section-2.1): - * Alphabetical characters: `a`-`z`, `A`-`Z` (decoded from `%41`-`%5A` and `%61`-`%7A`) - * Digit characters: `0`-`9` (decoded from `%30`-`%39`) - * hyphen `-` (`%2D`), period `.` (`%2E`), underscore `_` (`%5F`), and tilde `~` (`%7E`) -* These reserved characters are not encoded or decoded: `: / ? # [ ] @ ! $ & ' ( ) * + , ; =` -* Other characters, for example literal byte values, are percent encoded. -* Percent encoded representations are converted to upper case. -* URL paths are normalized according to the [Remove Dot Segments](https://tools.ietf.org/html/rfc3986#section-5.2.4) protocol. +- The following unreserved characters are [percent decoded](https://tools.ietf.org/html/rfc3986#section-2.1): + - Alphabetical characters: `a`-`z`, `A`-`Z` (decoded from `%41`-`%5A` and `%61`-`%7A`) + - Digit characters: `0`-`9` (decoded from `%30`-`%39`) + - hyphen `-` (`%2D`), period `.` (`%2E`), underscore `_` (`%5F`), and tilde `~` (`%7E`) +- These reserved characters are not encoded or decoded: `: / ? # [ ] @ ! $ & ' ( ) * + , ; =` +- Other characters, for example literal byte values, are percent encoded. +- Percent encoded representations are converted to upper case. +- URL paths are normalized according to the [Remove Dot Segments](https://tools.ietf.org/html/rfc3986#section-5.2.4) protocol. ## Cloudflare normalization diff --git a/src/content/docs/rules/normalization/index.mdx b/src/content/docs/rules/normalization/index.mdx index b5414c2f1f4ee0..b9912f9cd90787 100644 --- a/src/content/docs/rules/normalization/index.mdx +++ b/src/content/docs/rules/normalization/index.mdx @@ -3,10 +3,9 @@ pcx_content_type: concept title: URL normalization sidebar: order: 11 - --- -import { GlossaryTooltip, Render } from "~/components" +import { GlossaryTooltip, Render } from "~/components"; Cloudflare provides a URL normalization feature to modify the URLs of incoming requests so that they conform to a consistent formatting standard. @@ -14,14 +13,17 @@ When you enable URL normalization, all incoming URLs are normalized before they :::caution -When traffic is proxied via Cloudflare, essential request URL normalization is always applied regardless whether URL normalization is enabled for a specific zone. For example, you cannot disable the conversion of two or more adjacent slashes into a single slash in a request URL by turning off URL normalization. +When traffic is proxied via Cloudflare, essential request URL normalization is always applied regardless whether URL normalization is enabled for a specific zone. For example, you cannot disable the conversion of two or more adjacent slashes into a single slash in a request URL by turning off URL normalization. ::: URL normalization does not perform any redirects, and therefore it will not change the address displayed in the visitor's browser. The normalization operation, when enabled, occurs on the global network and affects Cloudflare features executed later and (optionally) the URL received at the origin server. - + -*** +--- ## Availability diff --git a/src/content/docs/rules/normalization/manage.mdx b/src/content/docs/rules/normalization/manage.mdx index 2657cd07a3433f..47ddf62d043d35 100644 --- a/src/content/docs/rules/normalization/manage.mdx +++ b/src/content/docs/rules/normalization/manage.mdx @@ -1,19 +1,16 @@ --- -title: Configure in the dashboard +title: Configure URL normalization in the dashboard pcx_content_type: how-to sidebar: order: 4 -head: - - tag: title - content: Configure URL normalization in the dashboard + label: Configure in the dashboard description: How to configure URL normalization in the Cloudflare dashboard. - --- 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and website. -2. Go to **Rules** > **Settings**. +2. Go to **Rules** > **URL Normalization**. - ![Available URL normalization settings in the Cloudflare dashboard](~/assets/images/rules/normalization/url-normalization-settings.png) +3. Configure the [available URL normalization settings](/rules/normalization/settings/). -3. Under **Configure Normalization**, configure the [available URL normalization settings](/rules/normalization/settings/). + ![Available URL normalization settings in the Cloudflare dashboard](~/assets/images/rules/normalization/url-normalization-settings.png) diff --git a/src/content/docs/rules/normalization/settings.mdx b/src/content/docs/rules/normalization/settings.mdx index c61fec8ef8072f..2dc9dfd762a139 100644 --- a/src/content/docs/rules/normalization/settings.mdx +++ b/src/content/docs/rules/normalization/settings.mdx @@ -1,42 +1,35 @@ --- -title: Settings +title: URL normalization settings pcx_content_type: reference sidebar: order: 5 -head: - - tag: title - content: URL normalization settings - + label: Settings --- The Cloudflare dashboard provides the following settings to manage URL normalization: +- **Normalization type** (default: _RFC-3986_) + - Selects the type of normalization to perform: -* **Normalization type** (default: *RFC-3986*) - - * Selects the type of normalization to perform: - - * *RFC-3986* – Applies URL normalization strictly according to [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986). - - * *Cloudflare* – In addition to what is defined in RFC 3986, applies [extra URL normalization techniques](/rules/normalization/how-it-works/#cloudflare-normalization). - -* **Normalize incoming URLs** (default: *On*) + - _RFC-3986_ – Applies URL normalization strictly according to [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986). - * Configures the URLs of all incoming traffic to Cloudflare: + - _Cloudflare_ – In addition to what is defined in RFC 3986, applies [extra URL normalization techniques](/rules/normalization/how-it-works/#cloudflare-normalization). - * When enabled, all incoming URLs are normalized before they pass to subsequent Cloudflare features that can receive a URL as input, such as Page Rules, WAF custom rules, Workers, and Access. - * When disabled, incoming URLs are not normalized before passing to subsequent Cloudflare features. +- **Normalize incoming URLs** (default: _On_) -* **Normalize URLs to origin** (default: *Off*) + - Configures the URLs of all incoming traffic to Cloudflare: - * Configures URLs sent to the origin: + - When enabled, all incoming URLs are normalized before they pass to subsequent Cloudflare features that can receive a URL as input, such as Page Rules, WAF custom rules, Workers, and Access. + - When disabled, incoming URLs are not normalized before passing to subsequent Cloudflare features. - * When enabled, requests sent to the origin are normalized. - * When disabled, requests sent to the origin are not modified. +- **Normalize URLs to origin** (default: _Off_) - * You can only view and enable this option when **Normalize incoming URLs** is enabled. + - Configures URLs sent to the origin: + - When enabled, requests sent to the origin are normalized. + - When disabled, requests sent to the origin are not modified. + - You can only view and enable this option when **Normalize incoming URLs** is enabled. For examples of how these settings affect URL normalization, refer to the [URL normalization examples](/rules/normalization/examples/). diff --git a/src/content/docs/rules/url-forwarding/bulk-redirects/create-api.mdx b/src/content/docs/rules/url-forwarding/bulk-redirects/create-api.mdx index fd259ef0edbddf..00277f6f9b8648 100644 --- a/src/content/docs/rules/url-forwarding/bulk-redirects/create-api.mdx +++ b/src/content/docs/rules/url-forwarding/bulk-redirects/create-api.mdx @@ -1,11 +1,9 @@ --- pcx_content_type: how-to -title: Create via API +title: Create Bulk Redirects via API sidebar: order: 7 -head: - - tag: title - content: Create Bulk Redirects via API + label: Create via API description: Learn how to create Bulk Redirects using the Cloudflare API. --- diff --git a/src/content/docs/rules/url-forwarding/bulk-redirects/create-dashboard.mdx b/src/content/docs/rules/url-forwarding/bulk-redirects/create-dashboard.mdx index 0c9c3651c4c34d..20e452fc4dcfce 100644 --- a/src/content/docs/rules/url-forwarding/bulk-redirects/create-dashboard.mdx +++ b/src/content/docs/rules/url-forwarding/bulk-redirects/create-dashboard.mdx @@ -1,22 +1,29 @@ --- pcx_content_type: how-to -title: Create in the dashboard +title: Create Bulk Redirects in the dashboard sidebar: order: 6 -head: - - tag: title - content: Create Bulk Redirects in the dashboard - + label: Create in the dashboard --- -import { Details, Render } from "~/components" +import { Details, Render } from "~/components"; To create Bulk Redirects in the Cloudflare dashboard you must: 1. Create a Bulk Redirect List with one or more URL redirects. 2. Create a Bulk Redirect Rule to enable the URL redirects in the list. - +You can create Bulk Redirect Lists and Bulk Redirect Rules in the Cloudflare dashboard: + +- At the account level, in **Bulk Redirects**. +- At the zone level, in **Rules** > **Redirect Rules** (**Bulk Redirects** tab). + +However, the lists and rules only exist at the account level and every zone in the same account will show the same items. + + ## 1. Create a Bulk Redirect List @@ -30,7 +37,6 @@ To create Bulk Redirects in the Cloudflare dashboard you must: 5. You can import a CSV file containing several URL redirects or enter URL redirects one at a time in the dashboard. -
6. Drag and drop a CSV file containing URL redirects or select **browse** and select a CSV file. For more information on the file format, refer to [CSV file format](/rules/url-forwarding/bulk-redirects/reference/csv-file-format/). @@ -39,10 +45,8 @@ To create Bulk Redirects in the Cloudflare dashboard you must: 8. Select **Next**. -
-
9. Select **Or, manually add URL redirects**. @@ -53,7 +57,6 @@ To create Bulk Redirects in the Cloudflare dashboard you must: 12. Select **Next**. -
13. Review and edit the URL redirects you imported or created, and select **Next**. @@ -61,12 +64,15 @@ To create Bulk Redirects in the Cloudflare dashboard you must: 14. Select **Continue to Redirect Rules** to go to the rule creation page, and follow the instructions in the next section. You must create a Bulk Redirect Rule to enable the URL redirects you defined. :::note[Notes] - + + + ::: ## 2. Create a Bulk Redirect Rule 1. (Optional) If you are not using the Bulk Redirect List creation wizard according to the instructions in the previous section: + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account. 2. Go to Account Home > **Bulk Redirects**. 3. Select **Create Bulk Redirect Rule**. diff --git a/src/content/docs/rules/url-forwarding/bulk-redirects/how-it-works.mdx b/src/content/docs/rules/url-forwarding/bulk-redirects/how-it-works.mdx index cccba6a495128f..79f2b9d4fd1609 100644 --- a/src/content/docs/rules/url-forwarding/bulk-redirects/how-it-works.mdx +++ b/src/content/docs/rules/url-forwarding/bulk-redirects/how-it-works.mdx @@ -1,11 +1,9 @@ --- -title: How it works +title: How Bulk Redirects work pcx_content_type: concept sidebar: order: 4 -head: - - tag: title - content: How Bulk Redirects work + label: How it works --- For each incoming request, Cloudflare evaluates all URL redirects of each Bulk Redirect List that is enabled by a Bulk Redirect Rule. diff --git a/src/content/docs/rules/url-forwarding/single-redirects/create-api.mdx b/src/content/docs/rules/url-forwarding/single-redirects/create-api.mdx index 14fe18604572f1..256685b1e56f3a 100644 --- a/src/content/docs/rules/url-forwarding/single-redirects/create-api.mdx +++ b/src/content/docs/rules/url-forwarding/single-redirects/create-api.mdx @@ -1,11 +1,9 @@ --- pcx_content_type: how-to -title: Create rule via API +title: Create a redirect rule via API sidebar: order: 3 -head: - - tag: title - content: Create a redirect rule via API + label: Create rule via API --- import { Details, Render } from "~/components"; diff --git a/src/content/docs/rules/url-forwarding/single-redirects/create-dashboard.mdx b/src/content/docs/rules/url-forwarding/single-redirects/create-dashboard.mdx index d8527f59bae3e7..b2a77357032268 100644 --- a/src/content/docs/rules/url-forwarding/single-redirects/create-dashboard.mdx +++ b/src/content/docs/rules/url-forwarding/single-redirects/create-dashboard.mdx @@ -1,18 +1,16 @@ --- pcx_content_type: how-to -title: Create rule in the dashboard +title: Create a redirect rule in the dashboard sidebar: order: 2 -head: - - tag: title - content: Create a redirect rule in the dashboard + label: Create rule in the dashboard --- import { Render } from "~/components"; 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain. 2. Go to **Rules** > **Redirect Rules**. -3. To create a new empty redirect rule, select **Create rule**. To duplicate an existing rule, select the three dots next to it > **Duplicate**. +3. In the **Single Redirects** tab, select **Create rule** to create a new empty rule. To duplicate an existing rule, select the three dots next to it > **Duplicate**. 4. (Optional) Select one of the rule templates that address common use cases. Then, review and adjust the proposed rule configuration. 5. Enter a descriptive name for the rule in **Rule name**. 6. Under **When incoming requests match**, select one of the following options: diff --git a/src/content/docs/rules/url-forwarding/single-redirects/settings.mdx b/src/content/docs/rules/url-forwarding/single-redirects/settings.mdx index 04cb7ef7841ace..fcffaecce39ce3 100644 --- a/src/content/docs/rules/url-forwarding/single-redirects/settings.mdx +++ b/src/content/docs/rules/url-forwarding/single-redirects/settings.mdx @@ -1,11 +1,9 @@ --- -title: Available settings +title: Available redirect rules settings pcx_content_type: reference sidebar: order: 10 -head: - - tag: title - content: Available redirect rules settings + label: Available settings --- import { Details, Render } from "~/components"; diff --git a/src/content/docs/rules/url-forwarding/single-redirects/terraform-example.mdx b/src/content/docs/rules/url-forwarding/single-redirects/terraform-example.mdx index 0b0707c82c0eb0..98ab89f8114365 100644 --- a/src/content/docs/rules/url-forwarding/single-redirects/terraform-example.mdx +++ b/src/content/docs/rules/url-forwarding/single-redirects/terraform-example.mdx @@ -1,15 +1,12 @@ --- -title: Create rule using Terraform +title: Create a redirect rule using Terraform pcx_content_type: configuration sidebar: order: 4 -head: - - tag: title - content: Create a redirect rule using Terraform - + label: Create rule using Terraform --- -import { Render } from "~/components" +import { Render } from "~/components"; The following example defines a single redirect rule for a zone using Terraform. The rule creates a static URL redirect for visitors requesting the contacts page using an old URL.