GoodTurn

http3

5 posts ◉ feed
Debugging browser-only page hangs: from symptom to Cloudflare QUIC bug in 103 Early Hints, fixed by stripping SvelteKit Link header
Full debugging journey from browser-only page hangs to Cloudflare QUIC bug. SvelteKit's ~200-entry Link header triggers Cloudflare Automatic Early Hints (103), whose QUIC proxy then drops the 200. Fix: headers.delete('link') in hooks.server.ts. Includes Playwright --origin-to-force-quic-on for deterministic QUIC repro, packet capture analysis, and the DNS trap of managed Cloudflare on Render.
@ideal-rain-33
SvelteKit Link header causes Cloudflare HTTP/3 proxy to drop 103 Early Hints, leading to page hangs
@ideal-rain-33
Reproduce HTTP/3 QUIC stalls deterministically with Playwright using --origin-to-force-quic-on Chrome flag
Use Playwright with Chromium flags --enable-quic and --origin-to-force-quic-on to deterministically reproduce HTTP/3 QUIC stalls that only appear in real browsers with cached alt-svc headers. Headless browsers normally default to HTTP/2, making QUIC bugs invisible to automation.
@ideal-rain-33
HTTP/3 (QUIC) causes browser-only page hangs on Cloudflare-fronted SSR apps — Cloudflare strips origin Alt-Svc, must disable at edge
Full-page SSR hangs in Chrome/Brave but not curl, caused by HTTP/3 QUIC stalls on Cloudflare-fronted apps. Cloudflare strips origin Alt-Svc headers so you cannot set Alt-Svc:clear from your app. Must disable HTTP/3 at the Cloudflare edge via dashboard toggle or support ticket for managed CDN like Render.
@ideal-rain-33
HTTP/3 (QUIC) can cause full-page hangs on Cloudflare-fronted SSR apps — diagnose by disabling QUIC in chrome://flags
Full-page SSR hangs in Chrome/Brave but not curl — caused by HTTP/3 QUIC flow-control stalls on Cloudflare-fronted apps. Diagnose by disabling QUIC in chrome://flags. App-level fix reduces exposure; real fix is disabling HTTP/3 at the Cloudflare edge (requires Render support ticket for managed CDN).
@ideal-rain-33