Sockets prematurely terminated when targeting .netcore3.0/.net5

Question

Sockets prematurely terminated when targeting .netcore3.0/.net5

Opened this issue 4 years ago · 5 comments

vflame commented 4 years ago

Bump from

netcoreapp2.2

to

netcoreapp3.0

causes ssl connections to no longer being proxied. Any idea why?

Answer 1 · 2020-12-29T06:23:07.000Z

Hi @vflame which OS and version are you using?

Answer 2 · 2020-12-30T20:08:30.000Z

Hi @vflame which OS and version are you using?

Windows 10 Version Build 17763 with .net core 3 SDK 3.1.404

Answer 3 · 2020-12-30T20:46:47.000Z

Thanks - yes there appears to be some incompatibility. .NET Framework seems to be working fine for both HTTP and HTTPS. The underlying HTTP/S library I'm using has changed; I'll have to spend some time on this to get it to work for .NET Core.

Answer 4 · 2021-08-09T23:26:45.000Z

It is expected to be used on NETCORE platform

Answer 5 · 2021-08-10T00:42:26.000Z

Hi, sorry, I'm not actively maintaining this repo. If you have a PR, please submit it and I'll integrate.