[Suggestion] Kong 集成雷池拦截请求时，希望返回内容新增 request.id ，可追踪请求，有利于排查
Open
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?
源文档：KONG集成雷池
插件生效时返回的内容如下
{"code": 403, "success":false, "message": "blocked by Chaitin SafeLine Web Application Firewall", "event_id": "8b41a021ea9541c89bb88f3773b4da24"}
需求： 希望可以在内容中追加 request.id , 这在 Kong 网关日志中追踪请求链路时特别有帮助，尤其是在排查误封情况时
Why is it needed?
现在阶段 safeline 插件返回内容只提供了event_id，当被误封需要进行排查时总是很麻烦
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 with the linked KONG集成雷池 documentation and locate the SafeLine/Kong plugin path that produces the shown 403 response. Confirm how request.id is obtained and define completion as the blocked response including it alongside event_id, with the documented response updated.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100