Fix for headersTimeout and requestTimeout timers

 This commit includes a fix for handling headersTimeout and requestTimeout
that causes unexpected behavior if the http server is started on boot
 - the connections to the server can be closed immediately with the status HTTP 408

 This issue usually happens in IoT or embedded devices where
the reference timestamp (returned by uv_hrtime()) is counted since boot
and can be smaller than the headersTimeout or the requestTimeout value.

 Additionally added performance improvement to process the list of
connection only if one of the timers should be processed

Author: franciszek-koltuniuk-red

src/node_http_parser.cc

@@ -1108,9 +1108,13 @@ void ConnectionsList::Expired(const FunctionCallbackInfo<Value>& args) {
 
   const uint64_t now = uv_hrtime();
   const uint64_t headers_deadline =
-    headers_timeout > 0 ? now - headers_timeout : 0;
+    (headers_timeout > 0 && now > headers_timeout) ? now - headers_timeout : 0;
   const uint64_t request_deadline =
-    request_timeout > 0 ? now - request_timeout : 0;
+    (request_timeout > 0 && now > request_timeout) ? now - request_timeout : 0;
+
+  if (headers_deadline == 0 && request_deadline == 0) {
+    return args.GetReturnValue().Set(Array::New(isolate, 0));
+  }
 
   auto iter = list->active_connections_.begin();
   auto end = list->active_connections_.end();