Improve default error reporting (debug mode via middleware for error event)
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 20/100
- Issue 類型
- 功能
- 描述清晰度
- 需要釐清
- 活躍度
- 停滯
- 技術堆疊
- php
研究方向
Start with the proposal in issue #344 and the related documentation issue #342. No files, tests, or entry points are identified, and the behavior is still open to design decisions around debug output, proxy-aware IP limits, logging, and custom error handlers. Done cannot be defined until those choices are resolved.
由索引模型根據 Issue 內容生成。
描述
I've just filed #342 to improve documentation for error handling for invalid requests and invalid responses respectively. This is only a first step because this keeps coming up and I think we agree it's about time to add some better default error handing logic.
This ticket aims to serve as a base to discuss how "default error handling logic" could look like.
For instance, we might want to just dump any Exception/Throwable including the full stack trace, but this may leak some application details to the outside. We may want to limit this to certain IP ranges only, but this won't work behind a reverse proxy anymore. We may want to add a "debug" flag or a DebugMiddleware, but this requires some explicit choice. We may want to respect PHP's error_reporting value, but it's unclear if this is how people understanding this configuration. We may want to log to STDERR instead of the response message, but it's unclear what effect this could have on existing deployments. We may want to apply our "default error handling logic" only if no explicit error is given, but it's unclear if this is what people expect when they start adding custom error handling logic.
Any input is welcome 👍
- 主要語言
- PHP
- 星號
- 781
- 分支
- 166
- PR 合併指標
- 30 天內沒有已合併 PR
貢獻指南
這個儲存庫沒有索引到貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
reactphp/http 的其他 Issue
-
bug
難度 3/5 1-2 天 新手友好度 76/100
-
bug
難度 3/5 1-2 天 新手友好度 35/100
-
maintenance
難度 5/5 一週以上 新手友好度 20/100
-
new feature
難度 4/5 3-5 天 新手友好度 48/100
-
help wanted new feature
難度 5/5 一週以上 新手友好度 25/100
相似的 Issue
-
sync-en
難度 1/5 1-3 小時 新手友好度 85/100
-
sync-en
難度 1/5 1-3 小時 新手友好度 85/100
-
Перевод устарел
難度 1/5 1-3 小時 新手友好度 78/100
-
難度 1/5 1 小時以內 新手友好度 90/100
-
難度 2/5 1-3 小時 新手友好度 85/100