Proxying works now on Firefox even on Windows but we're still seeing very strange behaviour: after 60-70 requests, the server becomes unresponsive. After a couple of minutes the server will "unfreeze" and things will start happening again. Hard to describe, although I know it when I see it.
I suspect this is due to TCP socket closures in freedom-for-firefox; investigating.
该提问来源于开源项目：UWNetworksLab/uProxy-p2p
分享 Hmm, really weird.
While socket closing seems to be totally borked with the echo server sample app, I actually do see close notifications working in the SOCKS server -- only difference vs. Chrome is that I get it ~15 seconds after the close actually happens. Let's forget about echo server for now and test with the proxy...
Here's a script that grinds the proxy to a halt on Firefox in ~500 requests:
bash
i=0; while true; do echo $i; curl -s -x socks5h://localhost:9999 www.example.com > /dev/null; sleep 0.1; i=$((i + 1)); done
AFAICT, the datachannel pool never grows beyond 50 in size.
On Chrome, I seem to be able to get well past 1000 without any issue or apparent slowdown.
分享