Hello,
yes, the fact is that no RFC defines idle/keepalive timeout of TCP
connection. We can just guess the optimal value accroding to clients
reactions and server resources. At AS50242 we ended up with
net.tcp_in_idle=120s
Just a few ideas:
What about implementing different tcp_in_idle parameter for empty and
non-empty sessions?
What about implementing server-side TCP keepalive messages?
What about returning "Connection: keep-alive" header as Cloudflare
does? (I don't know for what, just to be sure :) )
Blažej