Skip to content
This repository has been archived by the owner on Sep 9, 2022. It is now read-only.

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

Open
bemasc opened this issue May 23, 2016 · 2 comments
Open

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

bemasc opened this issue May 23, 2016 · 2 comments
Assignees
@bemasc
Labels
bug

Comments

@bemasc
Copy link
Contributor

bemasc commented May 23, 2016

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").
@bemasc bemasc added the bug label May 23, 2016
@bemasc bemasc self-assigned this May 23, 2016
@bemasc bemasc mentioned this issue May 23, 2016
Open
@mrjingguo
Copy link

Hi, did you solved this problem?

@bemasc
Copy link
Contributor Author

bemasc commented Jan 9, 2017

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bemasc bemasc

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bemasc @mrjingguo