<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>API on Paul Coding</title>
    <link>https://blog.paulcoding.com/tags/api/</link>
    <description>Recent content in API on Paul Coding</description>
    <generator>Hugo -- 0.147.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 27 Sep 2026 16:10:27 +0700</lastBuildDate>
    <atom:link href="https://blog.paulcoding.com/tags/api/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Understanding Cloudflare Blocks: Postman vs. cURL and TLS Fingerprinting</title>
      <link>https://blog.paulcoding.com/posts/cloudflare-postman-tls-fingerprinting/</link>
      <pubDate>Sat, 26 Sep 2026 22:44:32 +0700</pubDate>
      <guid>https://blog.paulcoding.com/posts/cloudflare-postman-tls-fingerprinting/</guid>
      <description>&lt;style&gt;
  .gpt {
    font-size: 14px;
    font-style: italic;
    background: yellow;
    padding: 8px;
  }
&lt;/style&gt;

&lt;p&gt;
  &lt;span class=&#34;gpt&#34;&gt;⚠ Created by AI 🤖&lt;/span&gt;
&lt;/p&gt;

&lt;p&gt;If you have ever had your API requests blocked by Cloudflare when using &lt;strong&gt;Postman&lt;/strong&gt;, only to find that the exact same request works perfectly fine using &lt;strong&gt;cURL&lt;/strong&gt;, you are not alone. This behavior stems from how modern Web Application Firewalls (WAFs) distinguish between legitimate developers, browsers, and automated bots.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
