Skip to content

[Challenges] New dash #23366

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jul 1, 2025
Merged

[Challenges] New dash #23366

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4eaf070
new dash
patriciasantaana Jul 1, 2025
1e83903
edits
patriciasantaana Jul 1, 2025
e84f1c1
missing comma
patriciasantaana Jul 1, 2025
06ebfc0
Update src/content/partials/cloudflare-challenges/javascript-detectio…
patriciasantaana Jul 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions ...ocs/cloudflare-challenges/challenge-types/challenge-pages/challenge-passage.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,6 @@ sidebar:
order: 3
---


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.

### How it works
Expand All @@ -25,7 +24,7 @@ To update the Challenge Passage (and the value of the `cf_clearance` cookie):
1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com).
2. Select your account and domain.
3. Go to **Security** > **Settings**.
4. For **Challenge Passage**, select a duration.
4. For **Challenge Passage**, set a duration.

### Limitations

Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/cloudflare-challenges/challenge-types/javascript-detections.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ sidebar:
order: 3
---

import { Render } from "~/components"
import { Render, Tabs, TabItem } from "~/components"

<Render file="javascript-detections-definition" />

Expand Down
18 changes: 16 additions & 2 deletions src/content/partials/cloudflare-challenges/javascript-detections-enable.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,23 @@

---

To enable JavaScript Detections:
import { Tabs, TabItem, Steps } from '~/components';

1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
<Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">

To enable JavaScript detections:

<Steps>
1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
2. Go to **Security** > **Bots**.
3. Select **Configure Bot Management**.
4. For **JavaScript Detections**, switch the toggle to **On**.
</Steps>
</TabItem> <TabItem label="New dashboard" icon="rocket">
To enable JavaScript detections using the Bot traffic settings module:
<Steps>
1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
2. Go to **Security** > **Settings**.
3. Under your bot traffic plan configurations, select the edit icon for **JS detections** to enable it by switching the toggle to **On**.
</Steps>
</TabItem> </Tabs>
Loading