Skip to content

Commit 67caf1c

Browse files
patriciasantaanapatriciasantaana
committed
broken links
1 parent e3757e3 commit 67caf1c

File tree

10 files changed

+12
-12
lines changed

10 files changed

+12
-12
lines changed

‎src/content/docs/api-shield/get-started.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ Use the Cloudflare API to configure [JSON Web Tokens validation](/api-shield/sec
117117

118118
If your origin uses GraphQL, you may consider setting limits on GraphQL query size and depth.
119119

120-
[GraphQL malicious query protection](/api-shield/security/graphql-protection/configure/) scans your GraphQL traffic for queries that could overload your origin and result in a denial of service. Customers can build rules that limit the query depth and size of incoming GraphQL queries in order to block suspiciously large or complex queries.
120+
[GraphQL malicious query protection](/api-shield/security/graphql-protection/api/) scans your GraphQL traffic for queries that could overload your origin and result in a denial of service. Customers can build rules that limit the query depth and size of incoming GraphQL queries in order to block suspiciously large or complex queries.
121121

122122
For more information, refer to the [blog post](https://blog.cloudflare.com/protecting-graphql-apis-from-malicious-queries/).
123123

‎src/content/docs/api-shield/reference/terraform.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ resource "cloudflare_api_shield_operation" "post_image" {
6565
It is required to configure Endpoint Management if you want to set up Schema validation 2.0 using Terraform.
6666
:::
6767

68-
Refer to the example configuration below to manage [Schema validation 2.0](/api-shield/security/schema-validation/configure/) on your zone.
68+
Refer to the example configuration below to manage [Schema validation 2.0](/api-shield/security/schema-validation/api/) on your zone.
6969

7070
```tf title="Example configuration"
7171
# Schema that should be used for schema validation 2.0

‎src/content/docs/api-shield/security/jwt-validation/api.mdx‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -160,8 +160,8 @@ Token validation rules can be configured using the Cloudflare API or [dashboard]
160160
| `description` | A human-readable description that gives more details than `title` and helps to document it. | Log requests without a valid `authorization` header. | Limited to 500 characters. |
161161
| `action` | The Firewall Action taken on requests that do not meet `expression`. | `log` | Possible: `log` or `block` |
162162
| `enabled` | Enable or disable the rule. | `true` | Possible: `true` or `false` |
163-
| `expression` | The rule's security policy. | `is_jwt_valid ("00170473-ec24-410e-968a-9905cf0a7d03")` | Make sure to escape any quotes when creating rules using the Cloudflare API. <br /> Refer to [Define a security policy](/api-shield/security/jwt-validation/configure/#define-a-security-policy) below. |
164-
| `selector` | Configure what operations are covered by this rule. | | Refer to [Applying a rule to operations](/api-shield/security/jwt-validation/configure/#apply-a-rule-to-operations) below. |
163+
| `expression` | The rule's security policy. | `is_jwt_valid ("00170473-ec24-410e-968a-9905cf0a7d03")` | Make sure to escape any quotes when creating rules using the Cloudflare API. <br /> Refer to [Define a security policy](#define-a-security-policy) below. |
164+
| `selector` | Configure what operations are covered by this rule. | | Refer to [Applying a rule to operations](#apply-a-rule-to-operations) below. |
165165

166166
### Selectors
167167

@@ -179,7 +179,7 @@ To find the operation ID, refer to [Endpoint Management](/api-shield/management-
179179

180180
A request must also match an operation covered by this rule to trigger an action.
181181

182-
Refer to [Apply a rule to operations](/api-shield/security/jwt-validation/configure/#apply-a-rule-to-operations) for more information.
182+
Refer to [Apply a rule to operations](#apply-a-rule-to-operations) for more information.
183183
:::
184184

185185
A token validation rule's expression defines a security policy that a request must meet.

‎src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ For example, the following expression will extract the user claim from a token p
2121
lookup_json_string(http.request.jwt.claims["<TOKEN_CONFIGURATION_ID>"][0], "claim_name")
2222
```
2323

24-
Refer to [Configure JWT validation](/api-shield/security/jwt-validation/configure/) for more information about creating a token configuration.
24+
Refer to [Configure JWT validation](/api-shield/security/jwt-validation/api/) for more information about creating a token configuration.
2525

2626
## Create a Transform Rule
2727

‎src/content/docs/api-shield/security/schema-validation/api.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ curl --request PATCH "https://api.cloudflare.com/client/v4/zones/{zone_id}/api_g
107107
}
108108
```
109109

110-
When a schema is active, it executes the mitigation action specified for each operation. Refer to [change the default and operation-specific mitigation action](/api-shield/security/schema-validation/configure/#change-the-default-and-operation-specific-mitigation-action).
110+
When a schema is active, it executes the mitigation action specified for each operation. Refer to [change the default and operation-specific mitigation action](#change-the-default-and-operation-specific-mitigation-action).
111111

112112
### Add new operations to Endpoint Management
113113

‎src/content/docs/data-localization/metadata-boundary/graphql-datasets.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The table below shows a non-exhaustive list of GraphQL Analytics API fields that
2222
| Zaraz | | US and EU <br/>`zarazActionsAdaptiveGroups` <br/> `zarazTrackAdaptiveGroups` <br/> `zarazTriggersAdaptiveGroups` |
2323
| Application Security | Advanced Certificate Manager | US and EU <br/> Only the fields `clientSSLProtocol` and `ja3Hash` part of `httpRequestsAdaptive` and `httpRequestsAdaptiveGroups` |
2424
| Advanced DDoS Protection | | US and EU <br/> [`dosdAttackAnalyticsGroups`](/analytics/graphql-api/migration-guides/network-analytics-v2/node-reference/) <br/> [`dosdNetworkAnalyticsAdaptiveGroups`](/analytics/graphql-api/migration-guides/network-analytics-v2/node-reference/) <br/> [`flowtrackdNetworkAnalyticsAdaptiveGroups`](/analytics/graphql-api/migration-guides/network-analytics-v2/node-reference/) <br/> `advancedTcpProtectionNetworkAnalyticsAdaptiveGroups` <br/> `advancedDnsProtectionNetworkAnalyticsAdaptiveGroups` |
25-
| API Shield | | US and EU <br/> [`apiGatewayGraphqlQueryAnalyticsGroups`](/api-shield/security/graphql-protection/configure/#gather-graphql-statistics) <br/> `apiGatewayMatchedSessionIDsAdaptiveGroups` <br/> US only <br/> `apiRequestSequencesGroups` |
25+
| API Shield | | US and EU <br/> [`apiGatewayGraphqlQueryAnalyticsGroups`](/api-shield/security/graphql-protection/api/#gather-graphql-statistics) <br/> `apiGatewayMatchedSessionIDsAdaptiveGroups` <br/> US only <br/> `apiRequestSequencesGroups` |
2626
| Bot Management | | US and EU <br/>`httpRequestsAdaptive` <br/> [`httpRequestsAdaptiveGroups`](/analytics/graphql-api/migration-guides/graphql-api-analytics/) <br/> [`firewallEventsAdaptive`](/analytics/graphql-api/tutorials/querying-firewall-events/) <br/> [`firewallEventsAdaptiveGroups`](https://blog.cloudflare.com/how-we-used-our-new-graphql-api-to-build-firewall-analytics/) |
2727
| DNS Firewall | Same as DNS |
2828
| DMARC Management | | US and EU <br/> `dmarcReportsAdaptive` <br/> `dmarcReportsSourcesAdaptiveGroups` |

‎src/content/docs/security/settings.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ In the **API abuse** security module you can perform the following tasks:
6262
- Review information about [Endpoint Discovery](/api-shield/security/api-discovery/) (always enabled if included in your Enterprise subscriptions).
6363
- Enable [Sequence Discovery](/api-shield/security/sequence-analytics/) (requires that you configure a session identifier).
6464
- Enable [Schema Validation](/api-shield/security/schema-validation/) (requires that you upload a schema or apply a learned schema).
65-
- Enable [JWT Validation](/api-shield/security/jwt-validation/) (requires that you add a [JWT configuration](/api-shield/security/jwt-validation/configure/#token-configurations)).
65+
- Enable [JWT Validation](/api-shield/security/jwt-validation/) (requires that you add a [JWT configuration](/api-shield/security/jwt-validation/api/#token-configurations)).
6666

6767
:::note
6868
The API abuse module includes features and settings from [API Shield](/api-shield/) in the previous dashboard navigation structure.

‎src/content/docs/waf/custom-rules/use-cases/check-jwt-claim-to-protect-admin-user.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ head:
77
---
88

99
:::note
10-
To use claims inside a JSON Web Token (JWT), you must first set up a [token validation configuration](/api-shield/security/jwt-validation/configure/) in API Shield.
10+
To use claims inside a JSON Web Token (JWT), you must first set up a [token validation configuration](/api-shield/security/jwt-validation/api/) in API Shield.
1111
:::
1212

1313
This example configures additional protection for requests with a JSON Web Token (JWT) with a user claim of `admin`, based on the request's [attack score](/waf/detections/attack-score/).

‎src/content/docs/waf/rate-limiting-rules/parameters.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -225,7 +225,7 @@ If you use **Cookie value of** as a rate limiting rule characteristic, follow th
225225

226226
### Requirements for using claims inside a JSON Web Token (JWT)
227227

228-
To use claims inside a JSON Web Token (JWT), you must first set up a [token validation configuration](/api-shield/security/jwt-validation/configure/) in API Shield.
228+
To use claims inside a JSON Web Token (JWT), you must first set up a [token validation configuration](/api-shield/security/jwt-validation/api/) in API Shield.
229229

230230
## Configuration restrictions
231231

‎src/content/partials/api-shield/set-up-session-identifiers.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ import { Steps } from "~/components"
1313
:::note
1414
The session identifier cookie must comply with RFC 6265. Otherwise, it will be rejected.
1515

16-
If you are using a JWT claim, choose the [Token Configuration](/api-shield/security/jwt-validation/configure/#token-configurations) that will verify the JWT. Token Configurations are required to use JWT claims as session identifiers. Refer to [JWT Validation](/api-shield/security/jwt-validation/) for more information.
16+
If you are using a JWT claim, choose the [Token Configuration](/api-shield/security/jwt-validation/api/#token-configurations) that will verify the JWT. Token Configurations are required to use JWT claims as session identifiers. Refer to [JWT Validation](/api-shield/security/jwt-validation/) for more information.
1717
:::
1818
6. Enter the name of the session identifier.
1919
7. Select **Save**.

0 commit comments

Comments
 (0)