<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>HTTP 状态码 on 知识铺的博客</title>
    <link>https://index.zshipu.com/geek001/tags/HTTP-%E7%8A%B6%E6%80%81%E7%A0%81/</link>
    <description>Recent content in HTTP 状态码 on 知识铺的博客</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>zh-CN</language>
    <lastBuildDate>Thu, 10 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://index.zshipu.com/geek001/tags/HTTP-%E7%8A%B6%E6%80%81%E7%A0%81/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Uptime Kuma: Why HTTP 200 Can Hide a Broken App</title>
      <link>https://index.zshipu.com/geek001/post/20260910/Uptime-Kuma-Why-HTTP-200-Can-Hide-a-Broken-App/</link>
      <pubDate>Thu, 10 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://index.zshipu.com/geek001/post/20260910/Uptime-Kuma-Why-HTTP-200-Can-Hide-a-Broken-App/</guid>
      <description>Uptime Kuma 显示 UP 却依赖失败的场景 Uptime Kuma 能显示 UP，但端点却报告了失败的依赖。监控工具在检查服务可用性时，常常只关注基本连通性，而忽略了应用内部的实际健康状况。这种情况在实际运维中并不罕见，当依赖服务出现问题时，端点可能仍能正常响应请求，导致监控系统误判。 根据相关分析，Uptime Kuma 在这种</description>
    </item>
  </channel>
</rss>
