<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Api-Design on Compile My Mind</title>
    <link>https://www.compilemymind.com/tags/api-design/</link>
    <description>Recent content in Api-Design on Compile My Mind</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 23 Nov 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.compilemymind.com/tags/api-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Understanding HTTP Status Codes: What They Mean and How to Use Them</title>
      <link>https://www.compilemymind.com/posts/http-status-codes/</link>
      <pubDate>Sun, 23 Nov 2025 00:00:00 +0000</pubDate>
      <guid>https://www.compilemymind.com/posts/http-status-codes/</guid>
      <description>&lt;p&gt;HTTP status codes are the server&amp;rsquo;s vocabulary for telling clients what happened. Three digits. Completely standardized. And yet, they&amp;rsquo;re routinely misused in ways that break API clients, confuse security tools, and inadvertently leak information about your infrastructure.&lt;/p&gt;&#xA;&lt;p&gt;This guide covers what each status code category means, when to use specific codes, and a few security considerations that most tutorials skip.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;the-five-categories&#34;&gt;The Five Categories&lt;/h2&gt;&#xA;&lt;p&gt;Status codes are grouped by their first digit:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
