|
3 | 3 |
|
4 | 4 | --- |
5 | 5 |
|
6 | | -import { Steps } from "~/components" |
| 6 | +import { Steps, Tabs, TabItem } from "~/components" |
7 | 7 |
|
8 | | -<Steps> |
9 | | -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain. |
10 | | -2. Go to **Security** > **Security rules**. |
11 | | -3. To create a new empty rule, select **Create rule** > **Custom rules**. |
12 | | -4. Enter a descriptive name for the rule in **Rule name**. |
13 | | -5. Under **When incoming requests match**, use the **Field** drop-down list to filter by **Sequences** and select: |
14 | | - - Current Operation |
15 | | - - Previous Operations |
16 | | - - Elapsed time |
17 | | -6. Under **Value**, build a sequence by selecting a hostname for the sequence. |
18 | | -7. Select the checkbox for each endpoint in the order that you want them to appear in the sequence. |
19 | | -8. Set the time to complete. |
20 | | -9. Select **Save**. |
21 | | -10. Under **Then take action**, select the rule action in the **Choose action** dropdown. For example, selecting *Block* tells Cloudflare to refuse requests that match the conditions you specified. |
22 | | -11. (Optional) If you selected the Block action, you can configure a custom response. |
23 | | -12. Under **Place at**, select the order of when the rule will fire. |
24 | | -13. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**. |
25 | | -</Steps> |
| 8 | +<Tabs syncKey="dashNewNav"> |
| 9 | + <TabItem label="Old dashboard"> |
| 10 | + <Steps> |
| 11 | + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain. |
| 12 | + 2. Go to **Security** > **WAF** > **Custom rules**. |
| 13 | + 3. To create a new empty rule, select **Create rule**. |
| 14 | + 4. Enter a descriptive name for the rule in **Rule name**. |
| 15 | + 5. Under **When incoming requests match**, use the **Field** drop-down list and select: |
| 16 | + - Current Operation |
| 17 | + - Previous Operations |
| 18 | + - Elapsed time |
| 19 | + 6. Under **Value**, build a sequence by selecting a hostname for the sequence. |
| 20 | + 7. Select the checkbox for each endpoint in the order that you want them to appear in the sequence. |
| 21 | + 8. Set the time to complete. |
| 22 | + 9. Select **Save**. |
| 23 | + 10. Under **Then take action**, select the rule action in the **Choose action** dropdown. For example, selecting *Block* tells Cloudflare to refuse requests that match the conditions you specified. |
| 24 | + 11. (Optional) If you selected the Block action, you can configure a custom response. |
| 25 | + 12. Under **Place at**, select the order of when the rule will fire. |
| 26 | + 13. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**. |
| 27 | + </Steps> |
| 28 | + </TabItem> |
| 29 | + <TabItem label="New dashboard" icon="rocket"> |
| 30 | + <Steps> |
| 31 | + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain. |
| 32 | + 2. Go to **Security** > **Security rules**. |
| 33 | + 3. To create a new empty rule, select **Create rule** > **Custom rules**. |
| 34 | + 4. Enter a descriptive name for the rule in **Rule name**. |
| 35 | + 5. Under **When incoming requests match**, use the **Field** drop-down list to filter by **Sequences** and select: |
| 36 | + - Current Operation |
| 37 | + - Previous Operations |
| 38 | + - Elapsed time |
| 39 | + 6. Under **Value**, build a sequence by selecting a hostname for the sequence. |
| 40 | + 7. Select the checkbox for each endpoint in the order that you want them to appear in the sequence. |
| 41 | + 8. Set the time to complete. |
| 42 | + 9. Select **Save**. |
| 43 | + 10. Under **Then take action**, select the rule action in the **Choose action** dropdown. For example, selecting *Block* tells Cloudflare to refuse requests that match the conditions you specified. |
| 44 | + 11. (Optional) If you selected the Block action, you can configure a custom response. |
| 45 | + 12. Under **Place at**, select the order of when the rule will fire. |
| 46 | + 13. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**. |
| 47 | + </Steps> |
| 48 | + </TabItem> |
| 49 | +</Tabs> |
0 commit comments