
The www host that killed every login
A correct CSRF guard is useless at the edge if it forgets one hostname: the origin allowlist skipped www, and every signup and login POST died with a 403 before reaching the backend.
10 posts

A correct CSRF guard is useless at the edge if it forgets one hostname: the origin allowlist skipped www, and every signup and login POST died with a 403 before reaching the backend.

LifeLog switched domains, the redirect had to be host-aware so it wouldn't wipe the CSP, and the next day the watchdog auto-healed covers and orphan posts that had been generated outside of git.

Dogwalk spent nine hours with login and signup returning 403 because one environment line held an example value. What came next was worse: the secret the CI carried no longer existed, and only a fake pair could prove it.

Every contact form submission in production returned an error, and the form code was fine. Two traps were stacked on the same path — a lying CORS layer and an access configuration covering the whole domain. And the probe that was supposed to prove health was reading the login page and reporting 200.

A normalization rule at the edge layer was replacing the whole site's security policy with a two-line version, and only a test that hit real production noticed.

A single config line with a placeholder where the key should be killed production login and signup for almost nine hours — and the real key existed nowhere at all. The story of the best-intentioned lockout I ever shipped, and of the doctor that diagnoses a pair without ever seeing the secret.

Two machines, the same code, the same key. One got 200, the other took a 403 with error code: 1010. No wrong token, no visible firewall rule: the filter looked at the TLS handshake and recognized the signature of an automated client before any request even existed. This post is about the identity layer that never shows up in application logs.

Stripe with dead DNS 500s, a Portifolio Staging that no longer existed, a rate limit that blocked the wrong IP. The surgical cleanup that made the Capivara dashboard tell the truth again — and the CF-Connecting-IP that actually fixed the rate limit.

Exploring D1 sync — learnings, challenges and discoveries.

After weeks of coding, it was time to put Dogwalk online. The first deploy was a mix of euphoria and frustration — Vite + Cloudflare Pages.