Is your feature request related to a problem? Please describe.

Yes. The strict "Retry-After" mechanism introduced in v1.27.0 for handling 429/503 errors has unintentionally caused major issues for users of self-hosted services like RSSHub.

RSSHub, due to its web-scraping nature, can have frequent but short-lived failures, returning a 503 error. The new feature "punishes" a single failure by putting the entire RSSHub domain into a long cooldown period that cannot be manually overridden by the user.

This means even after I fix my RSSHub instance, I am locked out from updating any of my feeds from that source. Clicking "update" does nothing, which feels like a bug and is extremely frustrating. My FreshRSS experience was much better before version 1.27.0.

是的。自 1.27.0 版本起为处理 429/503 错误而引入的严格“Retry-After”机制，无意中为依赖 RSSHub 这类自托管服务的用户带来了严重问题。

RSSHub 由于其网络抓取的本质，可能会频繁地出现短暂的失败并返回 503 错误。这个新功能会因为一次失败，就将整个 RSSHub 域名置于一个漫长的、且用户无法手动覆盖的冷却期中。

这意味着，即使在我修复了我的 RSSHub 服务后，我仍然被锁定，无法更新任何来自该来源的订阅。点击“更新”按钮毫无反应，这感觉就像一个 bug，并且极其令人沮丧。在 1.27.0 版本之前，我的使用体验要好得多。

Use case

No response

Describe the solution you’d like

Please give control back to the administrator. I suggest one of the following solutions:

1. A "Force Refresh" option: Add a button or command that allows manually refreshing a feed while ignoring the cooldown period. This is the most needed feature.
2. A setting to disable the feature: Provide a global or per-domain setting to disable this strict backoff behavior for users who understand the risks (e.g., for their own self-hosted services).

请将控制权交还给管理员。我建议以下解决方案之一：

1. 一个“强制刷新”选项： 增加一个按钮或命令，允许在手动更新时忽略冷却期。这是最需要的功能。
2. 一个禁用该功能的设置： 提供一个全局或针对特定域名的设置，允许那些了解风险的用户（例如，针对他们自己的自托管服务）禁用这种严格的退避行为。

Describe alternatives you’ve considered

Downgrade to FreshRSS v1.26.3

降级到 FreshRSS v1.26.3 版本。

Additional context

No response