Skip to content

docs: 反代页补充 X-Forwarded-For 对节点地址与国家码的影响 #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stqfdyr merged 1 commit into from
Sep 16, 2026
Merged

docs: 反代页补充 X-Forwarded-For 对节点地址与国家码的影响 #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions src/content/install/reverse-proxy.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,13 +102,15 @@ Cloudflare 免费版那 100 MB 的上传上限也就不是天花板了，单个
### 3. 透传 `X-Forwarded-Proto` 和 `X-Forwarded-For`

- 没有 `X-Forwarded-Proto`，会话 cookie 拿不到 `Secure`
- 没有 `X-Forwarded-For`，登录限流按代理地址计数，所有人共用一个桶
- 没有 `X-Forwarded-For`，登录限流按代理地址计数，所有人共用一个桶；节点的连接来源也记成代理地址，
NAT 节点在面板上看不到公网地址，国家码也查不出来

hub 取 `X-Forwarded-For` 的最后一跳，且只在 peer 本身是本地地址时才采信。上面两种反代都是追加
而不是覆盖，所以链尾才是代理真正看到的地址。

本地反代前面再套一层 CDN 时，链尾是边缘的地址，所有访客共用一个限流桶。那种部署要让边缘自己写
客户端地址（Cloudflare 的 `CF-Connecting-IP`），再由本地反代覆盖 `X-Forwarded-For`：
本地反代前面再套一层 CDN 时，链尾是边缘的地址：所有访客共用一个限流桶，
面板上 NAT 节点显示的公网地址和国家码也都是边缘的。那种部署要让边缘自己写客户端地址
（Cloudflare 的 `CF-Connecting-IP`），再由本地反代覆盖 `X-Forwarded-For`：

```nginx
proxy_set_header X-Forwarded-For $http_cf_connecting_ip;
Expand Down