9/10/2023 0 Comments Pulltube proxy settings![]() ![]() Reading settings from macOS specifically would likely require portable programs to link in additional code specific to macOS, probably code written in Objective C. It works across all Unix systems in a portable way.It allows a great deal of specificity over proxy settings, including by protocol.It allows you to customize per-program which proxy to use or whether to use a proxy at all.The environment variables you're using here are the standard Unix way to express proxy settings in normal Unix tools, including command-line tools. Proxy setting in any GUI tool should result in subsequent setting of $http_proxy etc. Think that you have the same curl code being run under GNOME, KDE, XFCE, multitude of other Linux DEs, Windows native DE, MacOS native DE or in simple text-mode ssh session without any DE. Not the other way around, because there are myriads of possible ways how the graphical DEs would store proxy information and command line tools can't know all of them (also there's no sense in it, because by definition command line tools can run - and usually are run - without any graphical DE running). ![]() Whoever writes a GUI application to set proxy and wants that setting to be applicable to command-line tools, needs to conform to that standard. environment variables are *nix command-line standard. Simply your GUI proxy setting application is incompatible with command line tools. Does the GUI tool you use for setting "system proxy settings" set these variables for terminal sessions? If not, then you have the answer why the settings are not used. ![]() "system proxy settings" is exactly what you have set in your second example - that is, the variables $http_proxy etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |