Skip to content

[API Shield] JWT Validation/Volumetric abuse detection rate limiting use case #23770

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.

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 6 commits into from
Jul 18, 2025

Conversation

patriciasantaana
Copy link
Contributor

Summary

Adds 2 use cases for JWT validation and volumetric abuse detection to rate limit JWTs

Documentation checklist

  • The documentation style guide has been adhered to.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.

Copy link
Contributor

hyperlint-ai bot commented Jul 17, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Added use cases for JWT validation and volumetric abuse detection to enhance rate limiting capabilities.

  • Introduced two new use cases for JWT validation and volumetric abuse detection.
  • Updated documentation to include a new rendering component for rate limiting.
  • Clarified availability information for API Shield customers.

Modified Files

  • src/content/docs/api-shield/security/jwt-validation/index.mdx
  • src/content/docs/api-shield/security/volumetric-abuse-detection.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

Copy link
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/api-shield/ @patriciasantaana, @cloudflare/pcx-technical-writing
* @cloudflare/pcx-technical-writing

@patriciasantaana patriciasantaana marked this pull request as ready for review July 17, 2025 22:17
@patriciasantaana patriciasantaana requested a review from a team as a code owner July 17, 2025 22:17
@patriciasantaana patriciasantaana enabled auto-merge (squash) July 18, 2025 15:04
@patriciasantaana patriciasantaana merged commit e9b01f7 into production Jul 18, 2025
8 checks passed
@patriciasantaana patriciasantaana deleted the patricia/pcx18369-rl-rules-use-case branch July 18, 2025 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants