- java.net.preferIPv4Stack (default: false)
- If IPv6 is available on the operating system the underlying
native socket will be an IPv6 socket. This allows Java(tm)
applications to connect too, and accept connections from, both IPv4
and IPv6 hosts.
If an application has a preference to only use IPv4 sockets then
this property can be set to true. The implication is that the
application will not be able to communicate with IPv6 hosts.
-
- java.net.preferIPv6Addresses (default:
false)
- If IPv6 is available on the operating system the default
preference is to prefer an IPv4-mapped address over an IPv6
address. This is for backward compatibility reasons - for example
applications that depend on access to an IPv4 only service or
applications that depend on the %d.%d.%d.%d representation of an IP
address. This property can be set to try to change the preferences
to use IPv6 addresses over IPv4 addresses. This allows applications
to be tested and deployed in environments where the application is
expected to connect to IPv6 services.
-
- networkaddress.cache.ttl
- Specified in java.security to indicate the caching policy for
successful name lookups from the name service.. The value is
specified as integer to indicate the number of seconds to cache the
successful lookup.
A value of -1 indicates "cache forever". The default behavior is
to cache forever when a security manager is installed, and to cache
for an implementation specific period of time, when a security
manager is not installed.
-
- networkaddress.cache.negative.ttl (default:
10)
- Specified in java.security to indicate the caching policy for
un-successful name lookups from the name service.. The value is
specified as integer to indicate the number of seconds to cache the
failure for un-successful lookups.
A value of 0 indicates "never cache". A value of -1 indicates
"cache forever".
-
- http.proxyHost (default: <none>)
http.proxyPort (default: 80 if http.proxyHost
specified)
http.nonProxyHosts (default: <none>
ftp.proxyHost (default: <none>)
ftp.proxyPort (default: 80 if ftp.proxyHost
specified)
ftp.nonProxyHosts (default: <none>)
- http.proxyHost and http.proxyPort indicate the proxy server and
port that the http protocol handler will use.
http.nonProxyHosts indicates the hosts which should be connected
too directly and not through the proxy server. The value can be a
list of hosts, each seperated by a |, and in addition a wildcard
character (*) can be used for matching. For example:
-Dhttp.nonProxyHosts="*.example.com|localhost".
ftp.proxyHost and ftp.proxyPort indicate the proxy server and
port that the ftp protocol handler will use. ftp.nonProxyHosts is
similiar to http.nonProxyHosts and indicates the hosts that should
be connected too directly and not through the proxy server.
-
- http.agent (default: Java1.4.0)
- Indicates the User-Agent request header sent in http
requests.
-
- http.auth.digest.validateServer (default:
false)
http.auth.digest.validateProxy (default:
false)
http.auth.digest.cnonceRepeat (default: 5)
- These system properties modify the behavior of the HTTP digest
authentication mechanism. Digest authentication provides a limited
ability for the server to authenticate itself to the client (ie. by
proving that it knows the users password). However, not all servers
support this capability and by default the check is switched off.
The first two properties above can be set to true, to enforce this
check, for either authentication with an origin, or a proxy server
respectively.
It is not normally necessary to set the third property
(http.auth.digest.cnonceRepeat). This determines how many times a
cnonce value is reused. This can be useful when the MD5-sess
algorithm is being used. Increasing the value reduces the
computational overhead on both the client and the server by
reducing the amount of material that has to be hashed for each HTTP
request.
-
- http.auth.ntlm.domain:
- Similar to other HTTP authentication schemes, NTLM uses the
java.net.Authenticator class to acquire usernames and passwords
when they are needed. However, NTLM also needs the NT domain name.
There are three options for specifying the domain:
- Do not specify it. In some environments, the domain is not
actually required and the application need not specify it.
- The domain name can be encoded within the username by prefixing
the domain name followed by a back-slash '\' before the username.
With this method, existing applications that use the Authenticator
class do not need to be modified, so long as users are made aware
that this notation must be used.
- If a domain name is not specified as in method 2) and the
system property "http.auth.ntlm.domain" is defined, then the value
of this property will be used as the domain name.
-
- http.keepAlive (default: true)
- Indicates if keep alive (persistent) connections should be
supported. Persistent connections improve performance by allowing
the underlying socket connection be reused for multiple http
requests.
The default is true and thus persistent connections will be used
with http 1.1 servers. Set to 'false' to disable the use of
persistent connections.
-
- http.maxConnections (default: 5)
- If HTTP keep-alive is enabled, this value is the number of idle
connections that will be simultaneously kept alive,
per-destination.
-
