Browse Source

Clarify subnet/geo targeting specificity

pull/1001/head
Viranch Mehta 3 years ago
parent
commit
38e46c0565
No known key found for this signature in database GPG Key ID: D83D1392AE9F93B4
1 changed files with 3 additions and 2 deletions
  1. +3
    -2
      CHANGELOG.md

+ 3
- 2
CHANGELOG.md View File

@ -27,8 +27,9 @@
* Similarly, subnets must not be repeated in multiple rules, and various * Similarly, subnets must not be repeated in multiple rules, and various
subnet rules must be ordered such that most specific subnets appear before subnet rules must be ordered such that most specific subnets appear before
less specific ones; e.g. 10.1.1.0/24 must appear before 10.1.0.0/16. less specific ones; e.g. 10.1.1.0/24 must appear before 10.1.0.0/16.
* Subnet-only rules must appear before any subnet+geo rules, followed by
geo-only rules (and catch-all w/o any geos/subnets in the end)
* Subnet targeting is considered to be more specific than geo targeting, so
subnet-only rules must appear before any subnet+geo rules, followed by
geo-only rules (and catch-all rule w/o any geos/subnets in the end)
#### Stuff #### Stuff


Loading…
Cancel
Save