more broken links

patriciasantaana · patriciasantaana · commit 302b7f4d8bed · 2025-03-18T14:05:51.000-07:00
diff --git a/public/_redirects b/public/_redirects
@@ -547,7 +547,7 @@
 /fundamentals/customizations/building-custom-dashboards/index/ /fundamentals/api/building-custom-dashboards/ 301
 /fundamentals/customizations/ /fundamentals/ 301
 /fundamentals/security/cybersafe/ /fundamentals/reference/policies-compliances/cybersafe/ 301
-/fundamentals/security/challenge-passage/ /waf/tools/challenge-passage/ 301
+/fundamentals/security/challenge-passage/ /fundamentals/security/cloudflare-challenges/challenge-passage/ 301
 /fundamentals/glossary/ /fundamentals/reference/glossary/ 301
 /fundamentals/account-and-billing/login/ /fundamentals/setup/account/login/ 301
 /fundamentals/account-and-billing/account-maintenance/delete-account/ /fundamentals/subscriptions-and-billing/delete-account/ 301
diff --git a/src/content/docs/fundamentals/reference/under-attack-mode.mdx b/src/content/docs/fundamentals/reference/under-attack-mode.mdx
@@ -58,7 +58,7 @@ To preview what Under Attack mode looks like for your visitors:
 4. Go to **Custom Pages**.
 5. For **Managed Challenge / I'm Under Attack Mode™**, select **Custom Pages** > **View default**.
 
-The `Checking your browser before accessing...` challenge determines whether to block or allow a visitor within five seconds. After passing the challenge, the visitor does not observe another challenge until the duration configured in [Challenge Passage](/waf/tools/challenge-passage/).
+The `Checking your browser before accessing...` challenge determines whether to block or allow a visitor within five seconds. After passing the challenge, the visitor does not observe another challenge until the duration configured in [Challenge Passage](/fundamentals/security/cloudflare-challenges/challenge-passage/).
 
 ---
 
diff --git a/src/content/docs/security/settings.mdx b/src/content/docs/security/settings.mdx
@@ -100,7 +100,7 @@ This section allows you to configure multiple security-related settings. The fol
 | [JavaScript detections](/bots/reference/javascript-detections/)                                         | **Security** > **Bots** > **Configure Super Bot Fight Mode<br/>Security** > **Bots** > **Configure Bot Management** |
 | [Auto-update machine learning model](/bots/reference/machine-learning-models/)                          | **Security** > **Bots** > **Configure Bot Management**                                                              |
 | [Enable Security.txt](/security-center/infrastructure/security-file/)                                   | **Security** > **Settings**                                                                                         |
-| [Challenge Passage](/waf/tools/challenge-passage/)                                                      | **Security** > **Settings**                                                                                         |
+| [Challenge Passage](/fundamentals/security/cloudflare-challenges/challenge-passage/)                                                      | **Security** > **Settings**                                                                                         |
 | [Browser Integrity Check](/waf/tools/browser-integrity-check/)                                          | **Security** > **Settings**                                                                                         |
 | [Replace insecure JavaScript libraries](/waf/tools/replace-insecure-js-libraries/)                      | **Security** > **Settings**                                                                                         |
 | [Security Level](/waf/tools/security-level/)                                                            | **Security** > **Settings**                                                                                         |
diff --git a/src/content/docs/turnstile/concepts/pre-clearance-support.mdx b/src/content/docs/turnstile/concepts/pre-clearance-support.mdx
@@ -34,7 +34,7 @@ Refer to the [blog post](https://blog.cloudflare.com/integrating-turnstile-with-
 
 ## Clearance cookie duration
 
-Clearance cookies generated by the Turnstile widget will be valid for the time specified by the zone-level Challenge Passage value. To configure the Challenge Passage setting, refer to the [WAF documentation](/waf/tools/challenge-passage/).
+Clearance cookies generated by the Turnstile widget will be valid for the time specified by the zone-level Challenge Passage value. To configure the Challenge Passage setting, refer to the [WAF documentation](/fundamentals/security/cloudflare-challenges/challenge-passage/).
 
 ## Setup
 
diff --git a/src/content/docs/waf/troubleshooting/faq.mdx b/src/content/docs/waf/troubleshooting/faq.mdx
@@ -161,7 +161,7 @@ Block Amazon Web Services (AWS) and Google Cloud Platform (GCP) because of large
 
 Previously, unless you customize your front-end application, any AJAX request that is challenged will fail because AJAX calls are not rendered in the DOM.
 
-Now, you can [opt-in to Turnstile’s Pre-Clearance cookies](/turnstile/concepts/pre-clearance-support/). This allows you to issue a challenge early in your web application flow and pre-clear users to interact with sensitive APIs. Clearance cookies issued by a Turnstile widget are automatically applied to the Cloudflare zone that the Turnstile widget is embedded on, with no configuration necessary. The duration of the clearance cookie’s validity is controlled by the zone-specific configurable [Challenge Passage](/waf/tools/challenge-passage/) security setting.
+Now, you can [opt-in to Turnstile’s Pre-Clearance cookies](/turnstile/concepts/pre-clearance-support/). This allows you to issue a challenge early in your web application flow and pre-clear users to interact with sensitive APIs. Clearance cookies issued by a Turnstile widget are automatically applied to the Cloudflare zone that the Turnstile widget is embedded on, with no configuration necessary. The duration of the clearance cookie’s validity is controlled by the zone-specific configurable [Challenge Passage](/fundamentals/security/cloudflare-challenges/challenge-passage/) security setting.
 
 ### Why would I not find any failed challenges?
 
diff --git a/src/content/docs/waf/troubleshooting/samesite-cookie-interaction.mdx b/src/content/docs/waf/troubleshooting/samesite-cookie-interaction.mdx
@@ -59,7 +59,7 @@ If you require a specific `SameSite` configuration in your session affinity cook
 
 ## Known issues with SameSite and `cf_clearance` cookies
 
-When a visitor solves a [challenge](/fundamentals/security/cloudflare-challenges/) presented due to a [WAF custom rule](/waf/custom-rules/) or an [IP Access rule](/waf/tools/ip-access-rules/), a `cf_clearance` cookie is set in the visitor's browser. The `cf_clearance` cookie has a default lifetime of 30 minutes, which you can configure via [Challenge Passage](/waf/tools/challenge-passage/).
+When a visitor solves a [challenge](/fundamentals/security/cloudflare-challenges/) presented due to a [WAF custom rule](/waf/custom-rules/) or an [IP Access rule](/waf/tools/ip-access-rules/), a `cf_clearance` cookie is set in the visitor's browser. The `cf_clearance` cookie has a default lifetime of 30 minutes, which you can configure via [Challenge Passage](/fundamentals/security/cloudflare-challenges/challenge-passage/).
 
 Cloudflare uses `SameSite=None` in the `cf_clearance` cookie so that visitor requests from different hostnames are not met with later challenges or errors. When `SameSite=None` is used, it must be set in conjunction with the `Secure` flag.
 
