Foresight News 路由失效

[jv43]

Routes

/foresightnews
/foresightnews/article
/foresightnews/news
/foresightnews/column/1

Full routes

/foresightnews
/foresightnews/article
/foresightnews/news
/foresightnews/column/1

Related documentation

https://docs.rsshub.app/new-media.html#foresightnews

What is expected?

期望能正常获取 Foresight News 的精选资讯、文章、快讯等内容。

目前所有 /foresightnews 系列路由均返回 403（Fetch Failed），无法获取任何数据。

What is actually happening?

所有 /foresightnews/* 路由均返回 403 Forbidden（Fetch Failed）。

路由实现调用了 https://api.foresightnews.pro/v2/feed（精选）或 https://api.foresightnews.pro/v1/articles（文章）、https://api.foresightnews.pro/v1/news（快讯）等 API，返回结果以 base64 + zlib 压缩编码。

问题分析

从代码看（lib/routes/foresightnews/util.tsx + lib/utils/request-rewriter/fetch.ts），RSSHub 发出的请求：

1. Referer 被硬编码为 API 的 origin：Referer: https://api.foresightnews.pro
2. User-Agent 和一组 sec-ch-ua、sec-fetch-* 等浏览器头由 header-generator 动态生成（Node undici 栈）
3. 无 Cookie

从同一台服务器上用浏览器可直接访问 https://api.foresightnews.pro/v2/feed?size=50，但 RSSHub 请求被 403。怀疑原因是：

• Referer 行为不一致：官方前端从 https://foresightnews.pro/ 调用 API 时，Referer 应为主站域名，但 RSSHub 的 wrappedFetch 将 Referer 设为请求 URL 自身的 origin（即 https://api.foresightnews.pro），可能触发来源校验。
• TLS / HTTP 指纹差异：Node undici 的 TLS 客户端指纹（JA3 等）与真实浏览器不同，可能触发 Cloudflare 或其他 WAF 的客户端指纹检测。
• 服务器出口 IP 信誉：RSSHub 实例部署 IP 可能已被目标站拉黑。

建议排查方向

1. 将 Referer 改为与官方前端一致（https://foresightnews.pro/）
2. 检查是否涉及 Origin 校验（如有，补充 Origin: https://foresightnews.pro）
3. 若上述均无效，可能需评估是否切换到 Puppeteer/浏览器方案（或添加代理选项供用户自行绕过）

Deployment information

Self-hosted

Deployment information (for self-hosted)

No response

Additional info

info: <-- GET /foresightnews
warn: Request https://api.foresightnews.pro/v2/feed?size=50 with error 403 remaining retry attempts: 2
error: Error in /foresightnews: FetchError: [GET] "https://api.foresightnews.pro/v2/feed?size=50": 403 Forbidden
info: --> GET /foresightnews 503 578ms
info: <-- GET /foresightnews
warn: Request https://api.foresightnews.pro/v2/feed?size=50 with error 403 remaining retry attempts: 2
error: Error in /foresightnews: FetchError: [GET] "https://api.foresightnews.pro/v2/feed?size=50": 403 Forbidden
info: --> GET /foresightnews 503 610ms
info: <-- GET /foresightnews
warn: Request https://api.foresightnews.pro/v2/feed?size=50 with error 403 remaining retry attempts: 2
error: Error in /foresightnews: FetchError: [GET] "https://api.foresightnews.pro/v2/feed?size=50": 403 Forbidden
info: --> GET /foresightnews 503 630ms
info: <-- GET /foresightnews
warn: Request https://api.foresightnews.pro/v2/feed?size=50 with error 403 remaining retry attempts: 2
error: Error in /foresightnews: FetchError: [GET] "https://api.foresightnews.pro/v2/feed?size=50": 403 Forbidden
info: --> GET /foresightnews 503 622ms
info: <-- GET /foresightnews
warn: Request https://api.foresightnews.pro/v2/feed?size=50 with error 403 remaining retry attempts: 2
error: Error in /foresightnews: FetchError: [GET] "https://api.foresightnews.pro/v2/feed?size=50": 403 Forbidden
info: --> GET /foresightnews 503 610ms
info: <-- GET /foresightnews
warn: Request https://api.foresightnews.pro/v2/feed?size=50 with error 403 remaining retry attempts: 2
error: Error in /foresightnews: FetchError: [GET] "https://api.foresightnews.pro/v2/feed?size=50": 403 Forbidden
info: --> GET /foresightnews 503 863ms
info: <-- GET /foresightnews
warn: Request https://api.foresightnews.pro/v2/feed?size=50 with error 403 remaining retry attempts: 2
error: Error in /foresightnews: FetchError: [GET] "https://api.foresightnews.pro/v2/feed?size=50": 403 Forbidden
info: --> GET /foresightnews 503 725ms

This is not a duplicated issue

• I have searched existing issues to ensure this bug has not already been reported

[github-actions]

Searching for maintainers:

• /foresightnews: Route not found
• /foresightnews/article: @nczitzk
• /foresightnews/news: @nczitzk
• /foresightnews/column/1: Route not found

To maintainers: if you are not willing to be disturbed, list your username in scripts/workflow/test-issue/call-maintainer.js. In this way, your username will be wrapped in an inline code block when tagged so you will not be notified.

If all routes can not be found, the issue will be closed automatically. Please use NOROUTE for a route-irrelevant issue or leave a comment if it is a mistake.
如果所有路由都无法匹配，issue 将会被自动关闭。如果 issue 和路由无关，请使用 NOROUTE 关键词，或者留下评论。我们会重新审核。

[dosubot]

Hi @jv43! I'm Dosu and I’m helping the RSSHub team.

Your analysis looks spot-on. The root cause is very likely the Referer header. RSSHub's request rewriter automatically sets Referer to the request URL's origin [1], which in this case becomes https://api.foresightnews.pro — but the real frontend sends requests with Referer: https://foresightnews.pro. The API likely validates this and rejects mismatched referers with a 403.

The route code in util.tsx doesn't set any custom headers — it relies entirely on the automatic injection [2]:

const { data: response } = await got(apiUrl, {
    searchParams,
});

A fix would be to explicitly pass the correct Referer (and potentially Origin) in the route's request options:

const { data: response } = await got(apiUrl, {
    searchParams,
    headers: {
        referer: 'https://foresightnews.pro',
        // origin: 'https://foresightnews.pro',  // if needed
    },
});

Since RSSHub's header system only applies defaults when headers aren't already present [3], setting them explicitly in the route will override the automatic behavior. This should be a straightforward fix — though as you noted, if the target has also added TLS fingerprinting or IP reputation checks, the Referer fix alone may not be sufficient.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}