huahaofeng
/
aspnetcore
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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

This commit is contained in:
SteveSandersonMS 2017-02-09 14:28:18 +00:00
parent 66148dacf3
commit 4f7091c5d5
2 changed files with 1 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

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

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

@ -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); return isomorphicFetch(req, init);
} }