If the Chrome app starts the socks5 server and we try a curl request (to a server that has a keep-alive HTTP header?), say curl --socks5 localhost:1080 http://ifconfig.co, curl will never terminate. However, the same code does work in node, which suggests it's an issue with our net.js shim.
If the Chrome app starts the socks5 server and we try a curl request (to a server that has a keep-alive HTTP header?), say
curl --socks5 localhost:1080 http://ifconfig.co, curl will never terminate. However, the same code does work in node, which suggests it's an issue with ournet.jsshim.I copied over the relevant code to a node version here, for debugging purposes: https://www.dropbox.com/s/d262csa9s51xldr/node-colony-chrome.zip
Run it with
node test.jsand then the same curl command.