codekingpro/portable-devtools

1############################################################2#       Default Networking Configuration File3#4# This file may contain default values for the networking system properties.5# These values are only used when the system properties are not specified6# 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 Proxy11# settings when they do exist.12# Set it to 'true' to enable this feature and check for platform13# specific proxy settings14# Note that the system properties that do explicitly set proxies15# (like http.proxyHost) do take precedence over the system settings16# even if java.net.useSystemProxies is set to true.17 18java.net.useSystemProxies=false19 20#------------------------------------------------------------------------21# Proxy configuration for the various protocol handlers.22# DO NOT uncomment these lines if you have set java.net.useSystemProxies23# to true as the protocol specific properties will take precedence over24# system settings.25#------------------------------------------------------------------------26 27# HTTP Proxy settings. proxyHost is the name of the proxy server28# (e.g. proxy.mydomain.com), proxyPort is the port number to use (default29# value is 80) and nonProxyHosts is a '|' separated list of hostnames which30# should be accessed directly, ignoring the proxy server (default value is31# localhost & 127.0.0.1).32#33# http.proxyHost=34# http.proxyPort=8035http.nonProxyHosts=localhost|127.*|[::1]36#37# HTTPS Proxy Settings. proxyHost is the name of the proxy server38# (e.g. proxy.mydomain.com), proxyPort is the port number to use (default39# value is 443). The HTTPS protocol handlers uses the http nonProxyHosts list.40#41# https.proxyHost=42# https.proxyPort=44343#44# FTP Proxy settings. proxyHost is the name of the proxy server45# (e.g. proxy.mydomain.com), proxyPort is the port number to use (default46# value is 80) and nonProxyHosts is a '|' separated list of hostnames which47# should be accessed directly, ignoring the proxy server (default value is48# localhost & 127.0.0.1).49#50# ftp.proxyHost=51# ftp.proxyPort=8052ftp.nonProxyHosts=localhost|127.*|[::1]53#54# Socks proxy settings. socksProxyHost is the name of the proxy server55# (e.g. socks.domain.com), socksProxyPort is the port number to use56# (default value is 1080)57#58# socksProxyHost=59# socksProxyPort=108060#61# HTTP Keep Alive settings. remainingData is the maximum amount of data62# in kilobytes that will be cleaned off the underlying socket so that it63# can be reused (default value is 512K), queuedConnections is the maximum64# number of Keep Alive connections to be on the queue for clean up (default65# value is 10).66# http.KeepAlive.remainingData=51267# http.KeepAlive.queuedConnections=1068 69# Authentication Scheme restrictions for HTTP and HTTPS.70#71# In some environments certain authentication schemes may be undesirable72# when proxying HTTP or HTTPS.  For example, "Basic" results in effectively the73# cleartext transmission of the user's password over the physical network.74# This section describes the mechanism for disabling authentication schemes75# based on the scheme name. Disabled schemes will be treated as if they are not76# supported by the implementation.77#78# The 'jdk.http.auth.tunneling.disabledSchemes' property lists the authentication79# schemes that will be disabled when tunneling HTTPS over a proxy, HTTP CONNECT.80# The 'jdk.http.auth.proxying.disabledSchemes' property lists the authentication81# schemes that will be disabled when proxying HTTP.82#83# In both cases the property is a comma-separated list of, case-insensitive,84# authentication scheme names, as defined by their relevant RFCs. An85# implementation may, but is not required to, support common schemes whose names86# include: 'Basic', 'Digest', 'NTLM', 'Kerberos', 'Negotiate'.  A scheme that87# is not known, or not supported, by the implementation is ignored.88#89# Note: This property is currently used by the JDK Reference implementation. It90# is not guaranteed to be examined and used by other implementations.91#92#jdk.http.auth.proxying.disabledSchemes=93jdk.http.auth.tunneling.disabledSchemes=Basic94 95#96# Allow restricted HTTP request headers97#98# By default, the following request headers are not allowed to be set by user code99# in HttpRequests: "connection", "content-length", "expect", "host" and "upgrade".100# The 'jdk.httpclient.allowRestrictedHeaders' property allows one or more of these101# headers to be specified as a comma separated list to override the default restriction.102# The names are case-insensitive and white-space is ignored (removed before processing103# the list). Note, this capability is mostly intended for testing and isn't expected104# to be used in real deployments. Protocol errors or other undefined behavior is likely105# to occur when using them. The property is not set by default.106# Note also, that there may be other headers that are restricted from being set107# depending on the context. This includes the "Authorization" header when the108# relevant HttpClient has an authenticator set. These restrictions cannot be109# overridden by this property.110#111# jdk.httpclient.allowRestrictedHeaders=host112#113#114# Transparent NTLM HTTP authentication mode on Windows. Transparent authentication115# can be used for the NTLM scheme, where the security credentials based on the116# currently logged in user's name and password can be obtained directly from the117# operating system, without prompting the user. This property has three possible118# values which regulate the behavior as shown below. Other unrecognized values119# are handled the same as 'disabled'. Note, that NTLM is not considered to be a120# strongly secure authentication scheme and care should be taken before enabling121# this mechanism.122#123# Transparent authentication never used.124#jdk.http.ntlm.transparentAuth=disabled125#126# Enabled for all hosts.127#jdk.http.ntlm.transparentAuth=allHosts128#129# Enabled for hosts that are trusted in Windows Internet settings130#jdk.http.ntlm.transparentAuth=trustedHosts131#132jdk.http.ntlm.transparentAuth=disabled133 134#135# Maximum HTTP field section size that a client is prepared to accept136#137# jdk.http.maxHeaderSize=393216138#139# This is the maximum header field section size that a client is prepared to accept.140# This is computed as the sum of the size of the uncompressed header name, plus141# the size of the uncompressed header value, plus an overhead of 32 bytes for142# each field section line. If a peer sends a field section that exceeds this143# size a {@link java.net.ProtocolException ProtocolException} will be raised.144# This applies to all versions of the HTTP protocol. A value of zero or a negative145# value means no limit. If left unspecified, the default value is 393216 bytes146# or 384kB.147#148# Note: This property is currently used by the JDK Reference implementation. It149# is not guaranteed to be examined and used by other implementations.150#151# Default directory where automatically bound Unix domain server152# sockets are stored. Sockets are automatically bound when bound153# with a null address.154#155# The search order for the directory on Windows is:156#157# 1. System property "jdk.net.unixdomain.tmpdir"158#159# 2. Networking property "jdk.net.unixdomain.tmpdir" specified160#    in this file (not set by default)161#162# 3. The TEMP environment variable (the effective default)163#164# 4. The java.io.tmpdir system property165#166#jdk.net.unixdomain.tmpdir=167#168 169