-
Notifications
You must be signed in to change notification settings - Fork 9
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 #206
Comments
Any sign of proxy support being in the pipeline, or at least support for using the widnows defined proxy details? |
This feature is not in high demand. |
Someone on Linux reporting DNS problems with proxy: |
The next client alpha will have basic HTTP proxy support. SOCKS, pac, wpad, HTTPS proxies and proxy authentication will not supported at least initially. I'm not sure how common SOCKS is anymore. It's a completely different protocol. I believe really only SOCKS5 is used. pac and wpad are used for proxy auto-configuration. Evaluating pac requires running JavaScript. I wonder if the OS does pac and/or wpad on it's own. It would make more sense for the OS to do the auto discovery and use it to configure the manual proxy settings. It seems silly for every app on the system to have to know these protocols. I'm also not sure how common HTTPS proxies are. They require two layers of SSL encryption to connect to https websites. HTTP proxies have an address like Proxy authentication is probably not too hard to add. |
I think auto proxy configuration is handled by higher level platform specific apis. |
Completed as described above in v8.4.0 alpha. |
No description provided.
The text was updated successfully, but these errors were encountered: