PuppyProxy icon indicating copy to clipboard operation
PuppyProxy copied to clipboard

Published 20 hours ago • verified publisher icon jchristn

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

Open vflame opened this issue 4 years ago • 5 comments

Bump from

<TargetFrameworks>netcoreapp2.2</TargetFrameworks>

to

<TargetFrameworks>netcoreapp3.0</TargetFrameworks>

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

vflame avatar Dec 29 '20 05:12 vflame

Hi @vflame which OS and version are you using?

jchristn avatar Dec 29 '20 06:12 jchristn

Hi @vflame which OS and version are you using?

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

vflame avatar Dec 30 '20 20:12 vflame

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.

jchristn avatar Dec 30 '20 20:12 jchristn

It is expected to be used on NETCORE platform

yuzd avatar Aug 09 '21 23:08 yuzd

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

jchristn avatar Aug 10 '21 00:08 jchristn