-
Notifications
You must be signed in to change notification settings - Fork 15.1k
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
There is no support for authorization using sock5 proxy #11620
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. To help make it easier for us to investigate your issue, please follow the contributing guidelines. |
Is this feature now supported? |
1 similar comment
Is this feature now supported? |
Is this feature now supported? |
I don't see why it wouldn't be, Chromium supports it and we don't do anything special to disallow it. |
up similar problem in apps that use electron |
Expected behavior
There is support for authorization using sock5 proxy in session.setProxy({...}).
Example: using passwords and username in url: proxyRules: 'socks5://login:password@127.0.0.1:40001'
Actual behavior
There is no support for authorization using sock5 proxy. Event login on webContents not emitted.
The text was updated successfully, but these errors were encountered: