-
Notifications
You must be signed in to change notification settings - Fork 385
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
Support HTTP proxy instead #146
Comments
Another option is to support SOCKS5+TLS+Authetication There are some important facts about censorship systems (that people who live in the open world can't understand) and it's the importance of TLS re-encrypt and Authentication.
|
good idea It’s said that the Russian Gov can now figure out to whom you send messages by analyzing metadata. HTTPS proxy (with proper auth) would be a great solution |
Why is Whatsapp not supporting regular HTTP(S) proxies with Authentication??
Running HAProxy should be the last option because:
My recommendation is to add HTTPS proxy with authentication support to WhatsApp instead of this.
If you want to implement HTTPS proxy support in the WhatsApp application (please do so), it's important to implement it in the correct way and don't forget to implement simple important things like SNI, auth headers, and ..., just stick to RFC.
The reason I write this issue is:
The text was updated successfully, but these errors were encountered: