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

Add edgekit, a shared guard for the HTTP edge

未关闭
  • 哪里不对？
#19 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
18/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
go
领域
backend, security

调研方向

The payload names no files or tests in this repository. Start with the gouncer proxy-list package it mentions and the standard library's cross-origin protection, which the proposal says to wrap. Settle the module's API for client address, scheme and host, the public address option, refusal logging, report-only mode and the dialer's address checks before writing code. Done means a new edgekit module on the standard library with tests for trusted-proxy resolution and refusals, agreed with the maintainers first.

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

描述

enhancement

Downstream applications need one shared guard for writes from other sites, forwarded headers and outbound calls.

Current state: one application carries its own cross-origin guard and forwarded header rules. Any other application would have to copy them. Each reads the proxy list through gouncer but parses its public address itself.

Proposal: a new edgekit module on the standard library only. It works out the client address, scheme and host once, from trusted proxies only. It wraps the standard cross-origin protection with an optional public address. It logs a reason for each refused write. It offers a report-only mode and lets the application write the refusal. A dialer refuses loopback, private and link-local addresses.

Trigger: a second application needs the guard.

主要语言
Go
星标
69
派生
3
平均合并
9 小时 11 分钟
30 天内合并 PR
38

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

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

gopherium/framework 的其他 Issue

查看 gopherium/framework 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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