Remove "Connection: keep-alive" workaround from domain-task, as it's not needed with .NET Core >= 1.1.0. Fixes aspnet#655

Author: SteveSandersonMS

src/Microsoft.AspNetCore.SpaServices/npm/domain-task/package.json

@@ -1,6 +1,6 @@
 {
   "name": "domain-task",
-  "version": "2.0.2",
+  "version": "2.0.3",
   "description": "Tracks outstanding operations for a logical thread of execution",
   "main": "index.js",
   "scripts": {

src/Microsoft.AspNetCore.SpaServices/npm/domain-task/src/fetch.ts

@@ -25,15 +25,6 @@ function issueRequest(baseUrl: string, req: string | Request, init?: RequestInit
         `);
     }
 
-    // Currently, some part of ASP.NET (perhaps just Kestrel on Mac - unconfirmed) doesn't complete
-    // its responses if we send 'Connection: close', which is the default. So if no 'Connection' header
-    // has been specified explicitly, use 'Connection: keep-alive'.
-    init = init || {};
-    init.headers = init.headers || {};
-    if (!init.headers['Connection']) {
-        init.headers['Connection'] = 'keep-alive';
-    }
-
     return isomorphicFetch(req, init);
 }