Repository navigation
Block blacklisted IP addresses - #82
Conversation
How it worksResolves #77. The approach follows the IP blocking added to Protagonist (private-protagonist#204), with the classes ported closely:
Where it applies
Other clients (e.g. Builder → Search API cache invalidation, which calls our own configured The check
Because this happens per connection it covers:
Blocked ranges
IPv4-mapped IPv6 addresses ( Precedence is: never-allowable → ConfigurationBoth APIs read the same section; values are CIDR only. {
"TextServices": {
"IpBlocking": {
"BlockedIpRanges": [ "10.0.0.0/8" ],
"AllowedIpRanges": [ "127.0.0.0/8", "::1/128" ]
}
}
}
Failure behaviourThe guard doesn't log; the host, resolved address and blocking range are carried on
Jobs are still accepted at Not in this PR
|
e545c20 to
b30f2c3
Compare
What does this change?
Resolves #77
This PR matches prior work in protaginst to block blacklisted ip's, like the loopback address. It also adds the ability to allow ip's blocked by default if required for local testing.
Configuration Changes
Note
This PR introduces configuration changes.
TextServices:IpBlocking:BlockedIpRanges[]TextServices:IpBlocking:AllowedIpRanges[]