🚀 Turning coffee into scalable code
I’m Insaf Nilam, a full-stack developer passionate about crafting clean, efficient, and future-ready software. I love solving complex problems, exploring new tech stacks, and sharing my learnings through blogs. When I’m not coding, I’m probably tweaking deployments, experimenting with microservices, or geeking out over cloud architecture.
Markdown supported · ⌘↵ to post
Edge Ops
Mixed content after a Cloudflare Tunnel cutover almost always means the app still emits cleartext absolute asset or API URLs while the browser arrived on a TLS public name. The tunnel (or edge) terminates TLS for visitors, so the origin must honour the forwarded proto and host — or be configured with an explicit public base URL — otherwise templates and redirects keep minting insecure scheme links that the browser blocks. Strip or rewrite hard-coded cleartext origins in HTML, JSON, and Location headers; keep WebSocket endpoints on the same public hostname and secure scheme the page was loaded with.
Ops prove-out from a clean browser profile: load the public hostname, open the console for mixed-content warnings, and compare page-source asset schemes against the address bar. Curl the same paths with the edge’s forwarded-proto style headers toward the origin and confirm redirects stay on the secure public name, not an internal compose hostname. If only some routes break, hunt templates or reverse-proxy Location rewrites that still assume cleartext on the loopback port the connector dials.