title: HTTP2 and NGINX - when would I use a keepalive directive?
body: <p>I am experimenting with migration to http/2. I have set up a Wordpress website and configured NGINX to serve it using http/2 (using SSL/TLS).</p>
  
  <p>My understanding of http/2 is that by default it uses one connection to transfer a number of files - rather than opening new connections and repeating SSL handshakes for each file.</p>
  
  <p>To achieve a similar effect for http/1.x, NGINX offered the keepalive directive.</p>
  
  <p>So does using the keepalive directive make sense when using http/2 exclusively? Checking my config files with "nginx -t" reports no errors when I include it. But does it have any effect? Benchmarking showed no difference. </p>