<story><title>Stop Wasting Connections, Use HTTP Keep-Alive</title><url>https://lob.com/blog/use-http-keep-alive</url></story><parent_chain></parent_chain><comment><author>hkolk</author><text>Better yet.. switch to http2 (where keep-alive is deprecated):
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;developer.mozilla.org&amp;#x2F;en-US&amp;#x2F;docs&amp;#x2F;Web&amp;#x2F;HTTP&amp;#x2F;Headers&amp;#x2F;Keep-Alive&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;developer.mozilla.org&amp;#x2F;en-US&amp;#x2F;docs&amp;#x2F;Web&amp;#x2F;HTTP&amp;#x2F;Headers&amp;#x2F;Ke...&lt;/a&gt;</text></comment>
<story><title>Stop Wasting Connections, Use HTTP Keep-Alive</title><url>https://lob.com/blog/use-http-keep-alive</url></story><parent_chain></parent_chain><comment><author>toast0</author><text>The hidden danger, mentioned in the article, is if the client sends a second request while the server closes an idle connection. Until http&amp;#x2F;2, the client can&amp;#x27;t tell if the server closed the connection before or after it received the request. Many servers send a hint about the idle time out, but few client libraries process it (that I&amp;#x27;ve seen). The larger the latency between server and client, the bigger deal this is.</text></comment>