Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 2 additions & 0 deletions src/content/docs/bots/reference/javascript-detections.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,8 @@ For more details on how to set up bot protection, see [Get started](/bots/get-st

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

<Render file="cf-clearance-cookie" />

## Limitations

### If you enabled Bot Management before June 2020
Expand Down
4 changes: 4 additions & 0 deletions src/content/docs/turnstile/get-started/pre-clearance.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ sidebar:

---

import { Render } from "~/components"

## Prerequisites

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.
Expand All @@ -15,6 +17,8 @@ The prerequisite is crucial for pre-clearance to function properly. If set up co

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

<Render file="cf-clearance-cookie" product="bots" />

## Enable pre-clearance on a new site

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
Expand Down
11 changes: 11 additions & 0 deletions src/content/partials/bots/cf-clearance-cookie.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
---
{}

---

:::note

[JavaScript detections](/bots/reference/javascript-detections/) are stored in the `cf_clearance` cookie.

The `cf_clearance` cookie cannot exceed the maximum size of 4096 bytes.
:::
Loading