On Thu, 2014-11-06 at 18:10 +0000, VanCutsem, Geoffroy wrote: > > I removed the proxy settings I set from the environment, but left the > > proxies > > and DNS settings in connman as they were, and also left the proxies set in > > xwalk.service alone as well. I needed to install an rpm using zypper, but > > the > > connection was refused, until I exported the https_proxy to the environment > > again. So it seems that connman isn't doing what it should be doing. > > It's most likely the other components that are not doing what they > should, i.e. query/use ConnMan instead of relying purely on > environment variables.
The open source solution to the problem is libproxy [1]. It handles the case of per-URL proxies (for example, accessing some hosts directly inside a company intranet and only external ones via proxy) and proxy changes during the runtime of a process. We don't have anything matching that in Tizen, at least as far as I know. In particular, libproxy is not part of Tizen, although several Tizen components already have support for it [2]. So all proposals are at best package-specific workarounds for a missing distro feature. [1] https://code.google.com/p/libproxy/ [2] https://code.google.com/p/libproxy/wiki/Applications -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
