mklnz
mklnz
Same here, still having the issue on Node v14.15.1 - will try @wubzz 's solution....
Having the same issue but from Auckland to New York, it doesn't go across the pacific. Edit: It turns out any time the line is going through the 180th meridian...
Thanks for that, good catch - "disableInitialPayloadWait": true on the client's server section fixed the issue What are the implications of disabling initial payload wait? Also to clarify, I meant...
I think making it a configuration option with an implicit default might be a good idea, I'll let you know if I encounter different init payloads
Does the new allowSegmentedFixedLengthHeader: true option allow a workaround to this issue?
I added the config in the socks5 client config by separating the tcp/udp listeners, and bumped up the payload size to a 81920 just to test but still getting the...
Apart from submitting to Microsoft which I have done, it might help trying to get an EV code signing certificate (although I'm unsure this actually helps). HOWEVER just a warning...
Does having an EV code signing certificate actually decrease the likelihood of being flagged as a false positive? I can't seem to find any concrete information on how it affects...
Same, the error is happening within an async server component
I'd like to know this also, been having a lot of color problems in Blink, where as I have everything set up correctly using base16 on macOS iTerm2