Skip to content

Clarify 15MB limit for WAF Content Scanning #22628

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

Open
wants to merge 1 commit into
base: production
Choose a base branch
from

Conversation

Vortexmind
Copy link
Contributor

The linked page goes to a Cloudflare Gateway page, which has different limits per plan. Adding this comment to clarify that WAF Content Scanning is subject to the 15MB limit on all plans.

The linked page goes to a Cloudflare Gateway page, which has different limits per plan. Adding this comment to clarify that WAF Content Scanning is subject to the 15MB limit on all plans.
@Vortexmind Vortexmind requested review from pedrosousa and a team as code owners May 23, 2025 08:44
Copy link
Contributor

hyperlint-ai bot commented May 23, 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

Clarified the 15MB limit for WAF Content Scanning across all plans.

  • Added a note specifying that the 15MB limit applies to all plans for WAF Content Scanning.
  • Updated caution section to include the 15MB size limit clarification.

Modified Files

  • src/content/docs/waf/detections/malicious-uploads/index.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.

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.

2 participants