Remote socket close should produce error -100, not error -2 #16

bemasc · 2016-05-23T18:20:39Z

Currently, "Socket closed by remote peer" is associated with error code -2 ("FAILURE"). This is incorrect; to match Chromium's behavior it should be error code -100 ("CONNECTION_FAILED").

mrjingguo · 2017-01-09T11:23:22Z

Hi, did you solved this problem?

bemasc · 2017-01-09T16:07:58Z

Here's a pull request that might help: #22

bemasc added the bug label May 23, 2016

bemasc self-assigned this May 23, 2016

bemasc mentioned this issue May 23, 2016

Frequent Socket Error -2 on Android UWNetworksLab/uProxy-p2p#2441

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Remote socket close should produce error -100, not error -2 #16

Remote socket close should produce error -100, not error -2 #16

bemasc commented May 23, 2016

mrjingguo commented Jan 9, 2017

bemasc commented Jan 9, 2017

Remote socket close should produce error -100, not error -2 #16

Remote socket close should produce error -100, not error -2 #16

Comments

bemasc commented May 23, 2016

mrjingguo commented Jan 9, 2017

bemasc commented Jan 9, 2017