Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Direct error through Caddy's error route

未关闭
#2,747 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
43/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
go, php
领域
backend, web-dev

调研方向

Start by reading the implementation and tests for FrankenPHP's error handling, then compare how Caddy's error route is used by the linked caddy-crowdsec-bouncer example, especially its enable_caddy_error option. The issue asks for an option to direct FrankenPHP level errors to that route so Caddy can serve a custom error page; done means the option works for those errors and is covered by tests.

由索引模型根据 Issue 内容生成。

描述

enhancement
Describe your feature request

Is your feature request related to a problem? Please describe.
As result of #2711 I am seeing frequent maximum request handling time exceeded pages, which are just black-on-white. This is not exactly consistent with whatever style a website can have, and thus it can potentially confuse users. While web-server failures generally should break the flow and standout, this is a bit much.

Describe the solution you'd like
Caddy has errors route, that allows "secondary" processing, including serving custom error pages (static or not). It would be nice to have an option to direct FrankenPHP-level errors to that route, to be able to customize the error page. Should be similar to enable_caddy_error in https://github.com/hslatman/caddy-crowdsec-bouncer

Describe alternatives you've considered
I can't think of any alternatives really. Maybe to catch the response on Caddy level somehow, perhaps based on combination of response headers. But that feels "messy", when there literally is a route to do handle error events in Caddy.

主要语言
Go
星标
11.4k
派生
499
平均合并
2 天 9 小时
30 天内合并 PR
40

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

php/frankenphp 的其他 Issue

查看 php/frankenphp 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。