Timedout when trying to dispatch to second interface · alexkirsz/dispatch-proxy#68

(2 留言) (0 反應) (0 負責人)CoffeeScript (3,490 star) (243 fork)batch import

good first issuehelp wanted

描述

#Tried on 2 wifi interfaces.

Download manager: aria2

On using socks, displays unsupported socks version 71

HTTP server started on localhost:8080 Dispatching to addresses 192.168.1.100@1, 192.168.2.8@1 request [c75a0c] http://dl2.mihanpix.com/Film/2016/Kung.Fu.Panda.3.2016.720p.BRrip.Exclusive.Farsi.Dubbed.(2Dooble).mkv dispatch [c75a0c] 192.168.1.100 end [c75a0c] clientRequest response [c75a0c] 200 request [8996a7] http://dl2.mihanpix.com/Film/2016/Kung.Fu.Panda.3.2016.720p.BRrip.Exclusive.Farsi.Dubbed.(2Dooble).mkv dispatch [8996a7] 192.168.2.8 end [8996a7] clientRequest request [7edd2c] http://dl2.mihanpix.com/Film/2016/Kung.Fu.Panda.3.2016.720p.BRrip.Exclusive.Farsi.Dubbed.(2Dooble).mkv dispatch [7edd2c] 192.168.1.100 end [7edd2c] clientRequest response [7edd2c] 200 request [32ac3c] http://dl2.mihanpix.com/Film/2016/Kammatti.Paadam.2016.DVDRip.x264.mkv dispatch [32ac3c] 192.168.2.8 end [32ac3c] clientRequest error [8996a7] clientRequest Error: connect ETIMEDOUT 104.31.64.79:80 at Object.exports._errnoException (util.js:1022:11) at exports._exceptionWithHostPort (util.js:1045:20) at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14) request [94f13c] http://dl2.mihanpix.com/Film/2016/Kammatti.Paadam.2016.DVDRip.x264.mkv dispatch [94f13c] 192.168.1.100 end [94f13c] clientRequest response [94f13c] 200 error [32ac3c] clientRequest Error: connect ETIMEDOUT 104.31.65.79:80 at Object.exports._errnoException (util.js:1022:11) at exports._exceptionWithHostPort (util.js:1045:20) at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14) ^C

貢獻者指南

技術棧: javascript
領域: backend
議題類型: bug
難度: 3
預計時間: 1-3 hours
活動狀態: stale
清晰度: needs investigation
前置要求: basic Node.js knowledgeunderstanding of HTTP proxies
新手友善度: 30
研究方向: Investigate the dispatch logic in the proxy code, specifically how connections are routed to different interfaces. Look for error handling around connection timeouts and see why the second interface fails while the first succeeds. The issue may be related to how sockets are created or reused. Check the relevant files such as 'lib/dispatch.js' or similar.