Sasha Smundak | 625f86b | 2019-10-04 16:15:03 -0700 | [diff] [blame] | 1 | ############################################################ |
| 2 | # Default Networking Configuration File |
| 3 | # |
| 4 | # This file may contain default values for the networking system properties. |
| 5 | # These values are only used when the system properties are not specified |
| 6 | # on the command line or set programmatically. |
| 7 | # For now, only the various proxy settings can be configured here. |
| 8 | ############################################################ |
| 9 | |
| 10 | # Whether or not the DefaultProxySelector will default to System Proxy |
| 11 | # settings when they do exist. |
| 12 | # Set it to 'true' to enable this feature and check for platform |
| 13 | # specific proxy settings |
| 14 | # Note that the system properties that do explicitly set proxies |
| 15 | # (like http.proxyHost) do take precedence over the system settings |
| 16 | # even if java.net.useSystemProxies is set to true. |
| 17 | |
| 18 | java.net.useSystemProxies=false |
| 19 | |
| 20 | #------------------------------------------------------------------------ |
| 21 | # Proxy configuration for the various protocol handlers. |
| 22 | # DO NOT uncomment these lines if you have set java.net.useSystemProxies |
| 23 | # to true as the protocol specific properties will take precedence over |
| 24 | # system settings. |
| 25 | #------------------------------------------------------------------------ |
| 26 | |
| 27 | # HTTP Proxy settings. proxyHost is the name of the proxy server |
| 28 | # (e.g. proxy.mydomain.com), proxyPort is the port number to use (default |
| 29 | # value is 80) and nonProxyHosts is a '|' separated list of hostnames which |
| 30 | # should be accessed directly, ignoring the proxy server (default value is |
| 31 | # localhost & 127.0.0.1). |
| 32 | # |
| 33 | # http.proxyHost= |
| 34 | # http.proxyPort=80 |
| 35 | http.nonProxyHosts=localhost|127.*|[::1] |
| 36 | # |
| 37 | # HTTPS Proxy Settings. proxyHost is the name of the proxy server |
| 38 | # (e.g. proxy.mydomain.com), proxyPort is the port number to use (default |
| 39 | # value is 443). The HTTPS protocol handlers uses the http nonProxyHosts list. |
| 40 | # |
| 41 | # https.proxyHost= |
| 42 | # https.proxyPort=443 |
| 43 | # |
| 44 | # FTP Proxy settings. proxyHost is the name of the proxy server |
| 45 | # (e.g. proxy.mydomain.com), proxyPort is the port number to use (default |
| 46 | # value is 80) and nonProxyHosts is a '|' separated list of hostnames which |
| 47 | # should be accessed directly, ignoring the proxy server (default value is |
| 48 | # localhost & 127.0.0.1). |
| 49 | # |
| 50 | # ftp.proxyHost= |
| 51 | # ftp.proxyPort=80 |
| 52 | ftp.nonProxyHosts=localhost|127.*|[::1] |
| 53 | # |
| 54 | # Gopher Proxy settings. proxyHost is the name of the proxy server |
| 55 | # (e.g. proxy.mydomain.com), proxyPort is the port number to use (default |
| 56 | # value is 80) |
| 57 | # |
| 58 | # gopher.proxyHost= |
| 59 | # gopher.proxyPort=80 |
| 60 | # |
| 61 | # Socks proxy settings. socksProxyHost is the name of the proxy server |
| 62 | # (e.g. socks.domain.com), socksProxyPort is the port number to use |
| 63 | # (default value is 1080) |
| 64 | # |
| 65 | # socksProxyHost= |
| 66 | # socksProxyPort=1080 |
| 67 | # |
| 68 | # HTTP Keep Alive settings. remainingData is the maximum amount of data |
| 69 | # in kilobytes that will be cleaned off the underlying socket so that it |
| 70 | # can be reused (default value is 512K), queuedConnections is the maximum |
| 71 | # number of Keep Alive connections to be on the queue for clean up (default |
| 72 | # value is 10). |
| 73 | # http.KeepAlive.remainingData=512 |
| 74 | # http.KeepAlive.queuedConnections=10 |
| 75 | |
| 76 | # Authentication Scheme restrictions for HTTP and HTTPS. |
| 77 | # |
| 78 | # In some environments certain authentication schemes may be undesirable |
| 79 | # when proxying HTTP or HTTPS. For example, "Basic" results in effectively the |
| 80 | # cleartext transmission of the user's password over the physical network. |
| 81 | # This section describes the mechanism for disabling authentication schemes |
| 82 | # based on the scheme name. Disabled schemes will be treated as if they are not |
| 83 | # supported by the implementation. |
| 84 | # |
| 85 | # The 'jdk.http.auth.tunneling.disabledSchemes' property lists the authentication |
| 86 | # schemes that will be disabled when tunneling HTTPS over a proxy, HTTP CONNECT. |
| 87 | # The 'jdk.http.auth.proxying.disabledSchemes' property lists the authentication |
| 88 | # schemes that will be disabled when proxying HTTP. |
| 89 | # |
| 90 | # In both cases the property is a comma-separated list of, case-insensitive, |
| 91 | # authentication scheme names, as defined by their relevant RFCs. An |
| 92 | # implementation may, but is not required to, support common schemes whose names |
| 93 | # include: 'Basic', 'Digest', 'NTLM', 'Kerberos', 'Negotiate'. A scheme that |
| 94 | # is not known, or not supported, by the implementation is ignored. |
| 95 | # |
| 96 | # Note: This property is currently used by the JDK Reference implementation. It |
| 97 | # is not guaranteed to be examined and used by other implementations. |
| 98 | # |
| 99 | #jdk.http.auth.proxying.disabledSchemes= |
| 100 | jdk.http.auth.tunneling.disabledSchemes=Basic |
| 101 | |
| 102 | # |
Colin Cross | bb0b310 | 2022-04-21 14:13:38 -0700 | [diff] [blame] | 103 | # Allow restricted HTTP request headers |
| 104 | # |
| 105 | # By default, the following request headers are not allowed to be set by user code |
| 106 | # in HttpRequests: "connection", "content-length", "expect", "host" and "upgrade". |
| 107 | # The 'jdk.httpclient.allowRestrictedHeaders' property allows one or more of these |
| 108 | # headers to be specified as a comma separated list to override the default restriction. |
| 109 | # The names are case-insensitive and white-space is ignored (removed before processing |
| 110 | # the list). Note, this capability is mostly intended for testing and isn't expected |
| 111 | # to be used in real deployments. Protocol errors or other undefined behavior is likely |
| 112 | # to occur when using them. The property is not set by default. |
| 113 | # Note also, that there may be other headers that are restricted from being set |
| 114 | # depending on the context. This includes the "Authorization" header when the |
| 115 | # relevant HttpClient has an authenticator set. These restrictions cannot be |
| 116 | # overridden by this property. |
| 117 | # |
| 118 | # jdk.httpclient.allowRestrictedHeaders=host |
| 119 | # |
| 120 | # |
Sasha Smundak | 625f86b | 2019-10-04 16:15:03 -0700 | [diff] [blame] | 121 | # Transparent NTLM HTTP authentication mode on Windows. Transparent authentication |
| 122 | # can be used for the NTLM scheme, where the security credentials based on the |
| 123 | # currently logged in user's name and password can be obtained directly from the |
| 124 | # operating system, without prompting the user. This property has three possible |
| 125 | # values which regulate the behavior as shown below. Other unrecognized values |
| 126 | # are handled the same as 'disabled'. Note, that NTLM is not considered to be a |
| 127 | # strongly secure authentication scheme and care should be taken before enabling |
| 128 | # this mechanism. |
| 129 | # |
| 130 | # Transparent authentication never used. |
| 131 | #jdk.http.ntlm.transparentAuth=disabled |
| 132 | # |
| 133 | # Enabled for all hosts. |
| 134 | #jdk.http.ntlm.transparentAuth=allHosts |
| 135 | # |
| 136 | # Enabled for hosts that are trusted in Windows Internet settings |
| 137 | #jdk.http.ntlm.transparentAuth=trustedHosts |
| 138 | # |
| 139 | jdk.http.ntlm.transparentAuth=disabled |