CORS and Rate Limiting: Where They Help and Hurt

CORS and rate limiting solve completely different problems, but they collide in production all the time. CORS decides which browser-based origins can read your responses. Rate limiting decides how often a client can hit your API. One is a browser enforcement layer. The other is an abuse-control and fairness layer. They look unrelated until your frontend starts getting mysterious TypeError: Failed to fetch errors right when users hit quota limits. ...

October 7, 2026 · 7 min · headertest.com

CORS for HTTP/3: Pros, Cons, and What Changes

CORS does not magically change because your API moved from HTTP/1.1 or HTTP/2 to HTTP/3. The policy model is the same. The headers are the same. The browser still decides whether frontend JavaScript can read the response. What does change is the transport underneath: QUIC instead of TCP, different connection behavior, different performance characteristics, and a few deployment surprises that show up right next to your CORS config. That distinction matters. I’ve seen teams expect HTTP/3 to “fix” flaky CORS behavior because requests feel different in DevTools. It won’t. If your Access-Control-Allow-Origin policy is wrong, it stays wrong at any HTTP version. ...

October 5, 2026 · 7 min · headertest.com

CORS and Opaque Response Filtering Reference

CORS gets blamed for a lot of things it didn’t do. Half the time the server is fine and the browser is blocking access on purpose. The other half, someone added mode: "no-cors" and made the problem harder to debug. This guide is the practical version: what the browser actually gives you, what “opaque” really means, and how to make cross-origin responses readable. The short version When your frontend calls another origin, the browser decides whether JavaScript can read the response. ...

August 19, 2026 · 6 min · headertest.com

CORS in Rust Actix-web: Options, Pros, and Pitfalls

CORS in Actix-web is one of those things that looks trivial until your frontend starts failing with mysterious preflight errors at 2 AM. Rust gives you strong guarantees around memory safety. CORS gives you sharp edges around browser behavior. Different problem space entirely. If you’re building APIs with Actix-web, you’ll usually end up choosing between a few practical CORS strategies: * for public APIs strict allowlists for browser apps dynamic origin handling for multi-tenant setups “just reflect the origin” hacks you probably shouldn’t ship I’ll compare those approaches, show where Actix-web fits well, and point out the tradeoffs that actually matter in production. ...

August 14, 2026 · 7 min · headertest.com

CORS Caching and Performance Optimization

CORS performance usually gets treated like background noise until your frontend starts making hundreds of API calls and every second request triggers an OPTIONS preflight. Then it becomes very obvious: bad CORS config can waste latency, server CPU, and CDN cache efficiency. I’ve seen teams obsess over query performance while every browser quietly burns extra round trips on preflights they could have avoided. This guide is the practical version: what gets cached, what does not, and what headers to set when you want cross-origin requests to be fast without turning your policy into mush. ...

June 2, 2026 · 6 min · headertest.com

CORS Mistakes in Retool Apps and How to Fix Them

Retool makes it deceptively easy to wire up APIs fast. That’s great right up until the browser starts yelling about CORS and half the team decides “the API is broken.” Usually, the API is fine. The browser is doing exactly what it should do, and your Retool app is running into the same cross-origin rules as any other frontend. I’ve seen the same mistakes over and over with Retool setups: wrong origin assumptions, broken preflight handling, credentials mixed with wildcards, and APIs that technically work in Postman but fail instantly in the browser. Here’s the stuff that trips people up most often, and how I’d fix it. ...

May 16, 2026 · 7 min · headertest.com

CORS for WebTransport: copy-paste server patterns

WebTransport sits in an odd spot for people who already know CORS. You expect the usual fetch() rules, preflights, and response headers. Then you try WebTransport over HTTP/3 and realize the model is related to CORS, but not the same shape. Browsers still care about origin-based access control, but WebTransport uses its own handshake rules instead of classic OPTIONS preflight. If you build browser-facing infrastructure, this distinction matters. A lot. ...

May 15, 2026 · 6 min · headertest.com

CORS for Server-Sent Events: What Actually Works

Server-Sent Events look deceptively simple. Open a stream, keep writing data: lines, and the browser keeps listening. Then you put that stream on another origin and suddenly you’re debugging CORS, cookies, proxies, and browser quirks at 2 a.m. I’ve hit this enough times that I now treat SSE as “simple transport, annoying edge cases.” The CORS part is one of those edge cases. What CORS means for SSE SSE uses the browser’s EventSource API: ...

May 11, 2026 · 7 min · headertest.com

CORS and Private Network Access for Web APIs

Browsers used to treat “public website calls my router or local dev box” as mostly a weird edge case. That changed. Private Network Access, or PNA, adds another browser-enforced check when a page on a less-private network tries to reach a more-private one. If you build APIs, admin panels, local device UIs, or anything that runs on localhost, your CORS setup now has a second layer to think about. The short version: ...

April 22, 2026 · 7 min · headertest.com

CORS for Webflow CMS: Copy-Paste Reference Guide

If you’re trying to call the Webflow CMS API from browser JavaScript, CORS is usually the first wall you hit. The short version: Webflow CMS API requests from the browser are a bad fit unless Webflow explicitly allows your origin. Even when the API works fine in Postman or curl, the browser enforces CORS and blocks the response before your code can touch it. This guide is the practical version: what CORS means for Webflow CMS, what will fail, what can work, and what to copy-paste. ...

April 20, 2026 · 7 min · headertest.com