Skip to content

Commit 63fbcdb

Browse files
challenges
1 parent 10db1c1 commit 63fbcdb

File tree

2 files changed

+29
-23
lines changed

2 files changed

+29
-23
lines changed

src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/challenge-passage.mdx

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,9 @@ sidebar:
55
order: 3
66
---
77

8+
import { Steps, DashButton } from "~/components"
9+
10+
811
When a visitor solves a [Cloudflare Challenge](/cloudflare-challenges/) - as part of a [WAF custom rule](/waf/custom-rules/) or [IP Access rule](/waf/tools/ip-access-rules/) - you can set the **Challenge Passage** to prevent them from having to solve future Challenges for a specified period of time.
912

1013
### How it works
@@ -21,10 +24,13 @@ By default, the `cf_clearance` cookie has a lifetime of 30 minutes. Cloudflare r
2124

2225
To update the Challenge Passage (and the value of the `cf_clearance` cookie):
2326

24-
1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com).
25-
2. Select your account and domain.
26-
3. Go to **Security** > **Settings**.
27-
4. For **Challenge passage**, set a timeout duration.
27+
<Steps>
28+
1. In the Cloudflare dashboard, go to the **Security Settings** page.
29+
30+
<DashButton url="/?to=/:account/:zone/security/settings" />
31+
2. Go to **Challenge passage**.
32+
3. Select the edit icon to set a timeout duration.
33+
</Steps>
2834

2935
### Limitations
3036

src/content/partials/cloudflare-challenges/javascript-detections-enable.mdx

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -3,23 +3,23 @@
33

44
---
55

6-
import { Tabs, TabItem, Steps } from '~/components';
6+
import { Tabs, TabItem, Steps, DashButton } from '~/components';
77

8-
<Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">
9-
10-
To enable JavaScript detections:
11-
12-
<Steps>
13-
1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
14-
2. Go to **Security** > **Bots**.
15-
3. Select **Configure Bot Management**.
16-
4. For **JavaScript Detections**, switch the toggle to **On**.
17-
</Steps>
18-
</TabItem> <TabItem label="New dashboard" icon="rocket">
19-
To enable JavaScript detections using the Bot traffic settings module:
20-
<Steps>
21-
1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
22-
2. Go to **Security** > **Settings**.
23-
3. Under your bot traffic plan configurations, select the edit icon for **JS detections** and turn **JavaScript Detections** on.
24-
</Steps>
25-
</TabItem> </Tabs>
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** > **Bots**.
13+
3. Select **Configure Bot Management**.
14+
4. For **JavaScript Detections**, switch the toggle to **On**.
15+
</Steps>
16+
</TabItem>
17+
<TabItem label="New dashboard" icon="rocket">
18+
<Steps>
19+
1. In the Cloudflare dashboard, go to the **Security Settings** page.
20+
21+
<DashButton url="/?to=/:account/:zone/security/settings" />
22+
2. Under your bot traffic plan configurations, select the edit icon for **JS detections** and turn **JavaScript Detections** on.
23+
</Steps>
24+
</TabItem>
25+
</Tabs>

0 commit comments

Comments
 (0)