From 63ca21a0069a5d7d3532e10a2162797f7a529018 Mon Sep 17 00:00:00 2001
From: Reed Allman <reed@rdallman.com>
Date: Sat, 13 Apr 2019 00:37:24 -0700
Subject: [PATCH] fix idle timeout issue

details of bug are here: https://github.com/nodejs/node/issues/13391
docs here: https://nodejs.org/dist/latest-v8.x/docs/api/http.html#http_server_keepalivetimeout

tl;dr is node set a 5s idle timeout. this does what go and java both seem to
do (have not checked python or ruby, though from what I know about python,
we are not doing this either) and doesn't have an idle timeout. since in this
case we do kinda trust that the client is using an idle timeout (it's fn),
this seems like the right policy anyway (if fn dies is something to consider,
but the least of our worries is fdk conns in that case, and we are killing fn
spawned containers on startup too). it should also be noted the client (fn) is
only using 1 conn per container.
---
 fn-fdk.js | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/fn-fdk.js b/fn-fdk.js
index 230804f..38f1ed9 100644
--- a/fn-fdk.js
+++ b/fn-fdk.js
@@ -288,7 +288,8 @@ function handleHTTPStream (fnfunction, options) {
   }
 
   let currentServer = http.createServer(functionHandler)
-    .listen(tmpFile, () => {
+  currentServer.keepAliveTimeout = 0 // turn off
+  currentServer.listen(tmpFile, () => {
       fs.chmodSync(tmpFile, '666')
       fs.symlinkSync(tmpFileBaseName, listenFile)
     })