New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BACKPORT] Falling back from fallback #6577
Conversation
Currenly I am getting this when set fallback to false.
Full Log:
I think the problem is here somewhere @kiminuo ? |
Could you please try with this commit: kiminuo@59b2957? |
It is working fine with this. It is a bit smelly, you see this as the final solution? |
I find it quite elegant actually as WW1 does not support switching from https to http and vice versa. We can probably come up with a different solution but I don't really have a better solution at the moment. If you have any other idea, please share it here. Obviously, we have much better Tor networking code in WW2 but I'm not sure how much time it would take to backport it. |
Code LGTM. |
I take a look at this again and it is good. Can you check this on master as well? We do not want to bump into this same issue again there. |
This PR trying to solve the problem that if the client's fallback mechanism is activated there is no going back for normal operation. We see use cases when users just start Wasabi and do mixing for days without further action. This feature can be a solution for them.