Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It doesn't silently drop, it sends a header indicating it's closed the TCP connection.

This is a pretty common pattern whereby you want keep-alive.for performance reasons, but you don't want clients running _too long_ creating hot spots on your load balancers.



What header? Our client was envoy and it's pretty standards compliant, and it just kept trying to use the connection.

Edit: I see that it is `connection: close` I wonder if that is new behaviour or if envoy did not honour it at the time we encountered the issue.

Thanks for the info!


Instead of closing the connection it sends a message stating that it is closed? Wow.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: