export HTTP_PROXY=http://username:[email protected]:8080
export http_proxy=${HTTP_PROXY}
export HTTPS_PROXY=https://username:[email protected]:8080
export https_proxy=${HTTPS_PROXY}

proxy_servers:
    http: http://proxy.example.com:8080
    https: https://proxy.example.com:8080

Acquire::http::Proxy "http://proxy.example.com:8080/";
Acquire::https::Proxy "https://proxy.example.com:8080/";
Acquire::ftp::Proxy "https://proxy.example.com:8080/";

[main]
...
proxy = https://proxy.example.com:8080

proxy = protocol://username:[email protected]:port

http_proxy = http://proxy.example.com:8080/
https_proxy = https://proxy.example.com:8080/
ftp_proxy = http://proxy.example.com:8080/

[proxyConfig]
http_proxy =  http://proxy.example.com:8080
https_proxy = https://proxy.example.com:8080

{
 "proxies":
 {
   "default":
   {
     "httpProxy": "http://proxy.example.com:8080",
     "httpsProxy": "http://proxy.example.com:8080",
     "noProxy": "*.test.example.com,.example2.com"
   }
 }
}

[Service]
Environment="HTTP_PROXY=http://proxy.example.com:8080/"
Environment="HTTPS_PROXY=https://proxy.example.com:8080/"

[Service]
Environment="HTTP_PROXY=http://proxy.example.com:8080/" "NO_PROXY=localhost,127.0.0.1,docker-registry.example.com,.corp"
Environment="HTTPS_PROXY=https://proxy.example.com:8080/" "NO_PROXY=localhost,127.0.0.1,docker-registry.example.com,.corp"

my_proxies = {
    'http':  '10.0.0.1:8080',
    'https': '10.0.0.1:8080',
}

requests.get(..., proxies = my_proxies )

my_proxies = {
    'http':  'https://user:[email protected]:8080',
    'https': 'https://user:[email protected]:8080',
}

requests.get(..., proxies = my_proxies )

import requests
import os

# TLS フォワード Proxy としてすべての TLS 接続が Proxy によって復号されるようなケース向け
ca_verify_file = '/some/where/local_ca.crt'
ca_verify = True

# 設定するデフォルト Proxy
my_http_proxy  = 'https://proxy.example.com:8080'
my_https_proxy = 'https://proxy.example.com:8080'

# 環境変数を参照
http_proxy  = os.getenv( 'HTTP_PROXY', default=my_http_proxy )
https_proxy = os.getenv( 'HTTPS_PROXY', default=my_https_proxy )

# requests に渡す Proxy のパラメータを生成
proxies = {
    'http':  http_proxy,
    'https': https_proxy,
}

# ターゲット URL
target_url = 'https://www.google.co.jp/search'

# Payload (ここでは、クエリ)
payload = {
    'q': 'python requests proxy'
}

try:
    # Proxy は proxies= 辞書型 を渡す
    r = requests.get(target_url, params=payload, proxies=proxies, verify=ca_verify)
except requests.ConnectionError as e:
    if type(e) == requests.exceptions.SSLError:
        # ローカルな root CA 証明書ファイルを指定
        # ca_verify_file を直接指定しないのは、後で ca_verify を検査することで、
        # どちらのモードで呼び出したのかを検査できるようにするため
        ca_verify = ca_verify_file
        r = requests.get(target_url, params=payload, proxies=proxies, verify=ca_verify)
    else:
        raise e

# 取得した内容の表示
print(r.text)

proxy_servers:
    http: https://proxy.example.com:8080
    https: https://proxy.example.com:8080

proxy_servers:
  'http://10.20.1.128': 'http://10.10.1.10:5323'

(base) C:\Users\localuser>conda config --stdin
proxy_servers:
  http: https://proxy.example.com:8080
  https: https://proxy.example.com:8080
^Z

(base) C:\Users\localuser>conda config --show proxy_servers
proxy_servers:
  http: https://proxy.example.com:8080
  https: https://proxy.example.com:8080

(base) C:\Users\localuser>

proxy_servers:
  http: https://proxy.example.com:8080
  https: https://proxy.example.com:8080

(base) C:\Users\localuser>type inputfile.txt
proxy_servers:
  http: https://proxy.example.com:8080
  https: https://proxy.example.com:8080

(base) C:\Users\localuser>type inputfile.txt | conda config --stdin

(base) C:\Users\localuser>conda config --show proxy_servers
proxy_servers:
  http: https://proxy.example.com:8080
  https: https://proxy.example.com:8080

(base) C:\Users\localuser>

group {
   tool {
     directive1 "value1";
     directive2 "value2";
   };
};

group::tool {
  directive1 "value1";
  directive2 "value2";
};

group::tool::drective1 "value1";
group::tool::drective2 "value2";

       ftp
           ftp::Proxy sets the default proxy to use for FTP URIs. It is
           in the standard form of ftp://[[user][:pass]@]host[:port]/.
           Per host proxies can also be specified by using the form
           ftp::Proxy::<host> with the special keyword DIRECT meaning
           to use no proxies. If no one of the above settings is
           specified, ftp_proxy environment variable will be used. To
           use an FTP proxy you will have to set the ftp::ProxyLogin
           script in the configuration file. This entry specifies the
           commands to send to tell the proxy server what to connect
           to.        以下略

   Proxy Configuration
       The environment variable http_proxy is supported for system wide
       configuration. Proxies specific to APT can be configured via the
       option Acquire::http::Proxy. Proxies which should be used only
       for certain hosts can be specified via
       Acquire::http::Proxy::host. Even more finegrained control can be
       achieved via proxy autodetection, detailed further below. All
       these options use the URI format
       scheme://[[user][:pass]@]host[:port]/. Supported URI schemes are
       socks5h (SOCKS5 with remote DNS resolution), http and https.
       Authentication details can be supplied via apt_auth.conf(5)
       instead of including it in the URI directly.

       The various APT configuration options support the special value
       DIRECT meaning that no proxy should be used. The environment
       variable no_proxy is also supported for the same purpose.

       以下略

OPTIONS
       The HTTPS protocol is based on the HTTP protocol, so all options
       supported by apt-transport-http(1) are also available via
       Acquire::https and will default to the same values specified for
       Acquire::http. This manpage will only document the options
       unique to https.

$ export ftp_proxy="https://proxy.example.com:8080"
$ export http_proxy="https://proxy.example.com:8080"
$ export https_proxy="https://proxy.example.com:8080"
$ export no_proxy="192.168.0.1,172.17.0.3,10.0.0.5"

Acquire::ftp::Proxy "https://proxy.example.com:8080/";
Acquire::http::Proxy "https://proxy.example.com:8080/";
Acquire::https::Proxy "https://proxy.example.com:8080/";

--setopt=proxy=https://proxy.example.com:8080

       --setopt=option=value
              Set  any  config option in yum config or repo files. For options
              in the global config just use:  --setopt=option=value  for  repo
              options use: --setopt=repoid.option=value

DESCRIPTION
       Yum uses a configuration file at /etc/yum.conf.

       Additional  configuration  files are also read from the directories set
       by the reposdir option (default is `/etc/yum.repos.d').  See the repos-
       dir option below for further details.
＜略＞
[main] OPTIONS
       The  [main]  section  must exist for yum to do anything. It consists of
       the following options:
       ＜略＞
        proxy URL to the proxy server that yum should use.  Set this  to
              `libproxy'  to  enable  proxy  auto  configuration via libproxy.
              Defaults to direct connection.

        proxy_username username to use for proxy

        proxy_password password for this proxy
＜略＞

[repository] OPTIONS
       The repository section(s) take the following form:

              Example: [repositoryid]
              name=Some name for this repository
              baseurl=url://path/to/repository/

              repositoryid  Must  be  a  unique  name for each repository, one
              word.
              ＜略＞

       proxy  URL  to  the  proxy  server  for  this repository. Set to
              '_none_' to disable the global proxy setting  for  this  reposi-
              tory. If this is unset it inherits it from the global setting

       proxy_username  username  to use for proxy.  If this is unset it
              inherits it from the global setting

       proxy_password password for this proxy.  If  this  is  unset  it
              inherits it from the global setting

[main]
...
proxy = https://proxy.example.com:8080

curl -x https://proxy.example.com:8080 ...

   -x, --proxy [protocol://]host[:port]
              Use the specified proxy.

              The proxy string can be specified with a protocol:// pre‐
              fix.  No protocol specified or http:// will be treated as
              HTTP  proxy.  Use  socks4://,  socks4a://,  socks5://  or
              socks5h://  to  request  a  specific  SOCKS version to be
              used.  (The protocol support was added in curl 7.21.7)

              HTTPS proxy support  via  https://  protocol  prefix  was
              added in 7.52.0 for OpenSSL, GnuTLS and NSS.

              Unrecognized  and  unsupported  proxy  protocols cause an
              error since 7.52.0.  Prior versions may ignore the proto‐
              col and use http:// instead.

              If  the port number is not specified in the proxy string,
              it is assumed to be 1080.

              This option overrides existing environment variables that
              set  the proxy to use. If there's an environment variable
              setting a proxy, you can set proxy to "" to override it.

              All operations that are performed over an HTTP proxy will
              transparently be converted to HTTP. It means that certain
              protocol specific operations might not be available. This
              is  not  the case if you can tunnel through the proxy, as
              one with the -p, --proxytunnel option.

              User and password that might be  provided  in  the  proxy
              string  are  URL decoded by curl. This allows you to pass
              in special characters such as @ by using %40 or pass in a
              colon with %3a.

              The proxy host can be specified the exact same way as the
              proxy environment variables, including the protocol  pre‐
              fix (http://) and the embedded user + password.

              If  this  option is used several times, the last one will
              be used.

proxy = protocol://username:[email protected]:port

              The default  config  file  is checked for in the following
              places in this order:

              1) curl tries to find the "home dir": It first  checks  for  the
              CURL_HOME and then the HOME environment variables. Failing that,
              it uses getpwuid() on Unix-like systems (which returns the  home
              dir  given the current user in your system). On Windows, it then
              checks for the APPDATA variable, or as a last resort the '%USER‐
              PROFILE%\Application Data'.

              2)  On  windows, if there is no _curlrc file in the home dir, it
              checks for one in the same dir the curl executable is placed. On
              Unix-like  systems,  it will simply try to load .curlrc from the
              determined home dir.

ENVIRONMENT
       The environment variables can be  specified  in  lower  case  or
       upper case. The lower case version has precedence. http_proxy is
       an exception as it is only available in lower case.

       Using an environment variable to set  the  proxy  has  the  same
       effect as using the -x, --proxy option.

       http_proxy [protocol://]<host>[:port]
              Sets the proxy server to use for HTTP.

       HTTPS_PROXY [protocol://]<host>[:port]
              Sets the proxy server to use for HTTPS.

       [url-protocol]_PROXY [protocol://]<host>[:port]
              Sets  the  proxy  server to use for [url-protocol], where
              the protocol is a protocol  that  curl  supports  and  as
              specified  in  a  URL.  FTP, FTPS, POP3, IMAP, SMTP, LDAP
              etc.

       ALL_PROXY [protocol://]<host>[:port]
              Sets the proxy server  to  use  if  no  protocol-specific
              proxy is set.

       NO_PROXY <comma-separated list of hosts>
              list  of  host names that shouldn't go through any proxy.
              If set to a asterisk '*' only, it matches all hosts.

              Since 7.53.0, this environment variable disable the proxy
              even   if   specify   -x,   --proxy   option.   That   is
              NO_PROXY=direct.example.com  curl  -x  http://proxy.exam‐
              ple.com http://direct.example.com accesses the target URL
              directly,   and   NO_PROXY=direct.example.com   curl   -x
              http://proxy.example.com     http://somewhere.example.com
              accesses the target URL through proxy.

$ wget -e http_proxy=http://proxy.example.com:8080 ...
Connecting to proxy.example.com:8080... connected.
Proxy request sent, awaiting response... 200 OK
...

OPTIONS
   ＜略＞
   Basic Startup Options
       ＜略＞
       -e command
       --execute command
           Execute command as if it were a part of .wgetrc.  A command thus
           invoked will be executed after the commands in .wgetrc, thus taking
           precedence over them.  If you need to specify more than one wgetrc
           command, use multiple instances of -e.

ENVIRONMENT
       Wget supports proxies for both HTTP and FTP retrievals.  The standard
       way to specify proxy location, which Wget recognizes, is using the
       following environment variables:

       http_proxy
       https_proxy
           If set, the http_proxy and https_proxy variables should contain the
           URLs of the proxies for HTTP and HTTPS connections respectively.

       ftp_proxy
           This variable should contain the URL of the proxy for FTP
           connections.  It is quite common that http_proxy and ftp_proxy are
           set to the same URL.

       no_proxy
           This variable should contain a comma-separated list of domain
           extensions proxy should not be used for.  For instance, if the
           value of no_proxy is .mit.edu, proxy will not be used to retrieve
           documents from MIT.

https_proxy = http://proxy.example.com:8080/
http_proxy = http://proxy.example.com:8080/
ftp_proxy = http://proxy.example.com:8080/

FILES
       /etc/wgetrc
           Default location of the global startup file.

       .wgetrc
           User startup file.

[proxyConfig]
http_proxy = <string that identifies the server proxy. When set, splunkd sends all HTTP requests through this proxy server. The default value is unset.> 
https_proxy = <string that identifies the server proxy. When set, splunkd sends all HTTPS requests through the proxy server defined here. If not set, splunkd uses the proxy defined in http_proxy. The default value is unset.>  
no_proxy = <string that identifies the no proxy rules. When set, splunkd uses the [no_proxy] rules to decide whether the proxy server needs to be bypassed for matching hosts and IP Addresses. Requests going to localhost/loopback address are not proxied. Default is "localhost, 127.0.0.1, ::1">

{
 "proxies":
 {
   "default":
   {
     "httpProxy": "http://127.0.0.1:3001",
     "httpsProxy": "http://127.0.0.1:3001",
     "ftpProxy": "http://127.0.0.1:3001",
     "noProxy": "*.test.example.com,.example2.com"
   }
 }
}

[Service]
Environment="HTTP_PROXY=http://proxy.example.com:8080/" "NO_PROXY=localhost,127.0.0.1,docker-registry.example.com,.corp"
Environment="HTTPS_PROXY=https://proxy.example.com:8080/" "NO_PROXY=localhost,127.0.0.1,docker-registry.example.com,.corp"

$ sudo systemctl daemon-reload
$ sudo systemctl restart docker

$ systemctl show --property=Environment docker
Environment=HTTP_PROXY=http://proxy.example.com:8080/