| 1 |
We currently have three proxy backends: |
| 2 |
|
| 3 |
* environment, used if one of several proxy environment variables are set |
| 4 |
* gnome, used if "GNOME" is present in `$XDG_CURRENT_DESKTOP` |
| 5 |
* libproxy, used otherwise |
| 6 |
|
| 7 |
The environment backend is based on how libproxy handles proxy environment |
| 8 |
variables, which has some differences from how other programs (e.g. libcurl) |
| 9 |
might interpret these variables. In particular, the `http_proxy` or `HTTP_PROXY` |
| 10 |
variables are used for *all* protocols, not just HTTP. This backend allows for |
| 11 |
basic proxy support even if running outside GNOME and built without libproxy. |
| 12 |
|
| 13 |
The GNOME backend uses the GNOME proxy settings, currently located under |
| 14 |
/system/proxy in dconf. Because all /system settings are deprecated, these |
| 15 |
settings will probably move somewhere else in the future. See |
| 16 |
https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues/27. |
| 17 |
|
| 18 |
Finally, libproxy provides the best level of proxy configuration support, |
| 19 |
including support for environments like Windows or KDE, which have their own |
| 20 |
system proxy settings. But libproxy has some serious problems that are difficult |
| 21 |
to fix, e.g. https://github.com/libproxy/libproxy/issues/81. Accordingly, this |
| 22 |
backend is used only if the other two are not suitable. |
| 23 |
|
| 24 |
The GNOME and libproxy backends can both be disabled at build time, if desired. |