Skip to content

API · 1 November 2026

Keep-alive connections stay open across Runtime releases

When a server's API process was replaced during a release, a request in progress on a keep-alive connection could be answered with connection: close, and the client had to open a new connection. The connection now moves to the new process between two requests, after the last response is sent in full, and stays open. Connections whose last request had a body, HTTP/1.0 connections, and connections whose response included connection: close are closed after their response instead, as before.

Same day.

Cut your cloud billby 75%.

No card to start. Billed by the second after.

Start free, no card