[Suggestion] custom response codes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 22.6k
- Forks
- 1.5k
- Avg merge
- 4h 30m
- Merged PRs (30d)
- 11
Description
What would you like to be added or improved?
I suggest introducing the ability to set arbitrary response codes (for example, 418), which will allow you to more flexibly configure restrictions and combine them with higher-level server restrictions.
Why is it needed?
For additional configuration of more flexible restriction mechanisms. The possibilities of combining with existing upstream restriction mechanisms
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
Start by tracing the existing WAF restriction response path and the configuration for upstream restrictions. Determine where response codes are selected and define how arbitrary codes such as 418 should combine with those restrictions; the work is done when the behavior is configurable and verified for the stated restriction scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100