<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cors on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/cors/</link>
    <description>Recent content in Cors on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 19 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/cors/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted CORS Proxy Services: cors-anywhere vs Caddy vs Nginx vs local-cors-proxy</title>
      <link>https://www.pistack.xyz/posts/2026-06-19-self-hosted-cors-proxy-services-cors-anywhere-caddy-nginx-guide/</link>
      <pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-19-self-hosted-cors-proxy-services-cors-anywhere-caddy-nginx-guide/</guid>
      <description>&lt;h2 id=&#34;why-you-need-a-self-hosted-cors-proxy&#34;&gt;Why You Need a Self-Hosted CORS Proxy&lt;/h2&gt;&#xA;&lt;p&gt;Cross-Origin Resource Sharing (CORS) is one of the most common pain points in web development. When your frontend JavaScript running on &lt;code&gt;localhost:3000&lt;/code&gt; tries to call an API on &lt;code&gt;api.example.com&lt;/code&gt;, the browser blocks the request unless the API server explicitly allows your origin. In development, testing, and even production scenarios where you don&amp;rsquo;t control the target API, a CORS proxy is the fastest way to unblock your workflow.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
