Skip to content

Commit fe394d3

Browse files
patriciasantaanadeadlypants1973
authored andcommitted
[Bots/Turnstile] JSD clearance cookie (#19463)
* jsd cookie * Update src/content/partials/bots/cf-clearance-cookie.mdx
1 parent 8e8261c commit fe394d3

File tree

3 files changed

+17
-0
lines changed

3 files changed

+17
-0
lines changed

src/content/docs/bots/reference/javascript-detections.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,8 @@ For more details on how to set up bot protection, see [Get started](/bots/get-st
2424

2525
<Render file="javascript-detections-implementation" />
2626

27+
<Render file="cf-clearance-cookie" />
28+
2729
## Limitations
2830

2931
### If you enabled Bot Management before June 2020

src/content/docs/turnstile/get-started/pre-clearance.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,8 @@ sidebar:
77

88
---
99

10+
import { Render } from "~/components"
11+
1012
## Prerequisites
1113

1214
To enable pre-clearance, you must ensure that the hostname of the Turnstile widget matches the zone with the WAF rules. During the Turnstile configuration setup in the Cloudflare dashboard, you can see the registered zones. Select the appropriate hostname from this list.
@@ -15,6 +17,8 @@ The prerequisite is crucial for pre-clearance to function properly. If set up co
1517

1618
For more details on managing hostnames, refer to the [Hostname Management documentation](/turnstile/concepts/hostname-management/).
1719

20+
<Render file="cf-clearance-cookie" product="bots" />
21+
1822
## Enable pre-clearance on a new site
1923

2024
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
{}
3+
4+
---
5+
6+
:::note
7+
8+
[JavaScript detections](/bots/reference/javascript-detections/) are stored in the `cf_clearance` cookie.
9+
10+
The `cf_clearance` cookie cannot exceed the maximum size of 4096 bytes.
11+
:::

0 commit comments

Comments
 (0)