Merged
Conversation
Providing invalid filter query parameters to API endpoints which support the legacy filters interface currently generates 500 errors. These errors pollute the logs when automated scrapers attempt to guess valid query parameters and repeatedly spam invalid queries. This PR improves the situation by simply ignoring invalid query parameters on these pages.
josephsnyder
approved these changes
Apr 2, 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
2 participants
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.
Providing invalid filter query parameters to API endpoints which support the legacy filters interface currently generates 500 errors. These errors pollute the logs when automated scrapers attempt to guess valid query parameters and repeatedly spam invalid queries. This PR improves the situation by simply ignoring invalid query parameters on these pages.