Package org.eclipse.aether.transport.jdk
Class JdkTransporterConfigurationKeys
java.lang.Object
org.eclipse.aether.transport.jdk.JdkTransporterConfigurationKeys
JDK Transport configuration keys.
- Since:
- 2.0.0
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final StringDeprecated.static final StringThe hard limit of maximum concurrent requests JDK transport can do.static final StringIf enabled (default), operator-configured request headers (aether.transport.http.headers) and preemptively appliedAuthorizationare only sent on requests targeting the repository origin (the scheme, host and port the repository URL denotes).static final StringIf enabled, restores the legacy behavior where the transporter'sAuthenticatorhanded out the repository (or proxy) credentials to any host that issued an authentication challenge - including hosts reached by following a redirect off the repository.static final Stringstatic final intstatic final booleanstatic final boolean -
Method Summary
-
Field Details
-
CONFIG_PROP_HTTP_VERSION
Deprecated.UseConfigurationProperties.HTTP_VERSIONinstead. This property is kept for backward compatibility and will be removed in future versions.Use string representation of HttpClient version enum "HTTP_2" or "HTTP_1_1" to set default HTTP protocol to use.- See Also:
- Sourced from:
RepositorySystemSession.getConfigProperties()- Value type:
String- Default value:
DEFAULT_HTTP_VERSION- Supports Repo ID Suffix:
- Yes
-
DEFAULT_HTTP_VERSION
- See Also:
-
CONFIG_PROP_MAX_CONCURRENT_REQUESTS
The hard limit of maximum concurrent requests JDK transport can do. This is a workaround for the fact, that in HTTP/2 mode, JDK HttpClient initializes this value to Integer.MAX_VALUE (!) and lowers it on first response from the remote server (but it may be too late). See JDK bug JDK-8225647 for details.- See Also:
- Sourced from:
RepositorySystemSession.getConfigProperties()- Value type:
Integer- Default value:
DEFAULT_MAX_CONCURRENT_REQUESTS- Supports Repo ID Suffix:
- Yes
-
DEFAULT_MAX_CONCURRENT_REQUESTS
- See Also:
-
CONFIG_PROP_UNSCOPED_AUTHENTICATION
If enabled, restores the legacy behavior where the transporter'sAuthenticatorhanded out the repository (or proxy) credentials to any host that issued an authentication challenge - including hosts reached by following a redirect off the repository. When disabled (the default), credentials are only returned when the challenging origin (protocol, host and port) matches the repository base URI, or, for proxy challenges, the configured proxy address.- Since:
- 2.0.23
- See Also:
- Sourced from:
RepositorySystemSession.getConfigProperties()- Value type:
Boolean- Default value:
DEFAULT_UNSCOPED_AUTHENTICATION- Supports Repo ID Suffix:
- Yes
-
DEFAULT_UNSCOPED_AUTHENTICATION
- See Also:
-
CONFIG_PROP_ORIGIN_SCOPED_HEADERS
If enabled (default), operator-configured request headers (aether.transport.http.headers) and preemptively appliedAuthorizationare only sent on requests targeting the repository origin (the scheme, host and port the repository URL denotes). The JDKHttpClientre-sends all user-set headers on every redirect hop it follows - including hops that leave the repository origin - so with this enabled the transporter configures the client withRedirect.NEVERand follows redirects itself, dropping those headers on any hop that leaves the origin. Disable only when a redirect target legitimately requires the configured headers; disabling restores the JDK client's own redirect handling (Redirect.NORMAL) and the legacy header replay.- Since:
- 2.0.23
- See Also:
- Sourced from:
RepositorySystemSession.getConfigProperties()- Value type:
Boolean- Default value:
DEFAULT_ORIGIN_SCOPED_HEADERS- Supports Repo ID Suffix:
- Yes
-
DEFAULT_ORIGIN_SCOPED_HEADERS
- See Also:
-
ConfigurationProperties.HTTP_VERSIONinstead.