Hi,
I am configuring Caddy as a reverse proxy in front of an external node application that handles real-time WebSocket traffic. While testing persistent connections across background endpoints, such as a free script testing tool, Caddy closes idle HTTP/2 streams after roughly 60 seconds and returns a 502 Bad Gateway response to the client. Has anyone configured custom transport timeouts inside the reverse_proxy directive to keep long-polling WebSocket sessions alive, and is there a recommended flush_interval setting in Caddyfile to prevent upstream disconnects without causing high CPU usage?