Closed jab closed 7 years ago
Hey @trevj, I merged your backwards compatibility changes into this branch, resolved the resulting conflicts, and corrected the socks session reference bookkeeping in a way that works with the backwards compatibility changes. If these changes are merged, GitHub should automatically mark your #2858 as merged since this branch includes those commits.
updated PR title to be more accurate
I tested pointing Firefox at this, browsing heavy pages, streaming video, and downloading a 100+MB file, and couldn't tell I was using a proxy. Do you get similarly good performance and stability?
This version should also work with legacy clients as well as the version in #2858, but worth testing just to make sure I didn't screw anything up when I merged/ported. I'll see if I can figure out how to get that streamlined run_pair.sh testing workflow you showed me set up!
First attempt: tried run_pair.sh node-stable node-stable
and appears to be stuck at "Waiting for getter to come up":
I tried with "chrome-stable firefox-stable" in case it was something wrong with my node image, and the same thing happened. I assume it shouldn't take this long for the getter to come up, and something's actually going wrong in some hidden way?
Wonderful, thanks for finding the fix! 👍
Regarding run_pair.sh
, try the -p
switch:
run_pair.sh -p node-stable node-stable
Excellent! I just ran this against a legacy Firefox-based server and it works just fine: fast, and I wasn't able to break it.
:+1:
Ah I see some lint errors to address - then we'll be good to go.
Thanks so much for the help testing, @trevj, so glad to hear it worked for you with a legacy Firefox peer! I've fixed the lint issues as discussed, so just merged. Psyched to get this in, uncertain future notwithstanding!
This change is