[suggestion] Is it possible to implement interception based on behavioral characteristics?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 22.6k
- Forks
- 1.5k
- Avg merge
- 4h 30m
- Merged PRs (30d)
- 11
Description
背景与遇到的问题
例如：
1、虽然访问地址正常，但不断变化User-Agent。
2、大量访问某一些特殊的地址
建议的解决方案
频率限制基于配合规则。
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not identify files, tests, or an entry point. First clarify how behavioral rules should combine with frequency limiting, including changing User-Agent values and repeated access to special paths. Done would require an agreed rule model and documented interception behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100