Skip to content

[CF1] gateway access firewall policy precedence #21680

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 3 commits into from
Apr 17, 2025
Merged

[CF1] gateway access firewall policy precedence #21680

merged 3 commits into from
Apr 17, 2025

Conversation

@deadlypants1973
Copy link
Contributor

@deadlypants1973 deadlypants1973 commented Apr 14, 2025

Summary

PCX-16816

Screenshots (optional)

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.
  • Files which have changed name or location have been allocated redirects.

@hyperlint-ai
Copy link
Contributor

hyperlint-ai bot commented Apr 14, 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

Updated the documentation regarding the order of precedence for Gateway access firewall policies, clarifying the behavior of Allow policies in relation to Access policies.

  • Clarified that Cloudflare recommends placing specific policies at the top of the list.
  • Added information about Access policies evaluating traffic to private IP addresses even if a Gateway Allow rule matches first.
  • Emphasized that a Gateway Allow policy does not override Access policies.

Modified Files

  • src/content/partials/cloudflare-one/gateway/order-of-precedence.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.

@github-actions
Copy link
Contributor

github-actions bot commented Apr 14, 2025 •
edited
Loading

Preview URL: https://f116fabe.preview.developers.cloudflare.com
Preview Branch URL: https://kate-fixes-gatewayaccess.preview.developers.cloudflare.com

@deadlypants1973 deadlypants1973 marked this pull request as ready for review April 14, 2025 17:03
@deadlypants1973 deadlypants1973 requested a review from a team as a code owner April 14, 2025 17:03
@deadlypants1973 deadlypants1973 merged commit b529027 into production Apr 17, 2025
12 checks passed
@deadlypants1973 deadlypants1973 deleted the kate/fixes-gatewayaccess branch April 17, 2025 12:53
RebeccaTamachiro pushed a commit that referenced this pull request Apr 21, 2025
@deadlypants1973 @kennyj42 @RebeccaTamachiro
[CF1] gateway access firewall policy precedence (#21680)
4e787e4 
* [CF1] gateway access firewall policy precedence

* Update src/content/partials/cloudflare-one/gateway/order-of-precedence.mdx

* Update order-of-precedence.mdx

---------

Co-authored-by: kennyj42 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@kennyj42 kennyj42 kennyj42 approved these changes

@angelampcosta angelampcosta angelampcosta approved these changes

Assignees

@pedrosousa pedrosousa

@dcpena dcpena

@haleycode haleycode

@patriciasantaana patriciasantaana

Labels

size/xs

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@deadlypants1973 @kennyj42 @angelampcosta @pedrosousa @dcpena @haleycode @patriciasantaana