Repository navigation
Publish Banned IP as the public signal name - #17
Merged
Merged
Conversation
Inbound rate_limited is no longer accepted. The stored column, digest canonical form, and HTTP 429 stay unchanged.
EgorMajj
approved these changes
Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
banned_ip(API, webhook, History, CSV, cabinet catalog).rate_limitedis rejected. Saved cabinet filters that stored that slug stop matching.is_rate_limited, the durable digest canonical form, and HTTP 429rate_limitedstay unchanged.Env
Human merge only
Post-merge ops
?rate_limited=is rejected;?banned_ip=truereadsis_rate_limited. New event digests still canonicalize torate_limited. Re-parsing an in-flight body that still containsrate_limiteddoes not set the flag.Test plan
go test ./...#Made with Cursor