Refused to set unsafe header "connection"

[chris-herring]

I've noticed this error in Safari (9.1.2) and found in domain-task the following:

    if (!init.headers['Connection']) {
        init.headers['Connection'] = 'keep-alive';
    }

I see Connection listed here as a forbidden header name in the fetch spec.

Can this be wrapped in a !isBrowser condition?

[SteveSandersonMS]

Thanks for reporting this. The Connection header was only needed to work around a bug in Kestrel on ASP.NET Core 1.0. Since we now depend on ASP.NET Core 1.1 where Kestrel no longer has that bug, the workaround is no longer needed.

So, I've published domain-task 2.0.3 which no longer contains this problematic logic.