https://bugs.winehq.org/show_bug.cgi?id=45255
Bug ID: 45255 Summary: Provide easy way to configure proxy (winecfg?) Product: Wine Version: 3.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winhttp Assignee: wine-bugs@winehq.org Reporter: luizluca@gmail.com Distribution: ---
Currently wine tries to automatically detect proxy.
It will:
1) use env vars (http_proxy) 2) try to detect automatic settings (wpad)
One can easily disable env vars unsetting them or make them empty (since wine 3.9). However, there is easy no way to disable automatic detection without directly editing registry (it is a binary entry) or installing IExplorer.
winecfg could have a tab or wine could have a new tool to set proxy settings, just like windows control panel applet. However, it should have an extra setting from what Windows already have: "Use system environment values".
https://bugs.winehq.org/show_bug.cgi?id=45255
--- Comment #1 from Hans Leidekker hans@meelstraat.net --- (In reply to Luiz Angelo Daros De Luca from comment #0)
Currently wine tries to automatically detect proxy.
It will:
- use env vars (http_proxy)
- try to detect automatic settings (wpad)
One can easily disable env vars unsetting them or make them empty (since wine 3.9). However, there is easy no way to disable automatic detection without directly editing registry (it is a binary entry) or installing IExplorer.
winecfg could have a tab or wine could have a new tool to set proxy settings, just like windows control panel applet. However, it should have an extra setting from what Windows already have: "Use system environment values".
We'd like to defer editing of proxy settings to the host system as much as possible. Wine is just another application.
Why would you want to disable wpad in Wine only?
https://bugs.winehq.org/show_bug.cgi?id=45255
tokktokk fdsfgs@krutt.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs@krutt.org
https://bugs.winehq.org/show_bug.cgi?id=45255
--- Comment #2 from Luiz Angelo Daros De Luca luizluca@gmail.com ---
We'd like to defer editing of proxy settings to the host system as much as possible. Wine is just another application.
Why would you want to disable wpad in Wine only?
Because bug 43783. I needed to use a transparent proxy strategy.
Wpad isn't a host config but a network one. What are the options to not use it? Map wpad.domain to 0.0.0.0 in hosts? Filter it in firewall?
Wine could, although, use the same strategy that Google chrome does and use current desktop environment settings. It will also work just fine.
https://bugs.winehq.org/show_bug.cgi?id=45255
--- Comment #3 from Hans Leidekker hans@meelstraat.net --- (In reply to Luiz Angelo Daros De Luca from comment #2)
We'd like to defer editing of proxy settings to the host system as much as possible. Wine is just another application.
Why would you want to disable wpad in Wine only?
Because bug 43783. I needed to use a transparent proxy strategy.
Understood, but we're interested in fixing these bugs so workarounds won't be needed.
Wpad isn't a host config but a network one. What are the options to not use it? Map wpad.domain to 0.0.0.0 in hosts? Filter it in firewall?
I'd say whether wpad is used or not is a host configuration option.
Wine could, although, use the same strategy that Google chrome does and use current desktop environment settings. It will also work just fine.
Yes, this is how we want support proxy settings. Hopefully we won't need separate implementations for each Linux desktop environment.
https://bugs.winehq.org/show_bug.cgi?id=45255
--- Comment #4 from Hans Leidekker hans@meelstraat.net --- Note that there's support for configuring IE proxy settings in Wine now (wine control -> Internet Settings -> Connections). These settings are used automatically for apps built against wininet. Apps built against winhttp have to implement this themselves by calling WinHttpGetIEProxyConfigForCurrentUser.
-
wine-bugs＠winehq.org