Class JettyTransporterConfigurationKeys

java.lang.Object
org.eclipse.aether.transport.jetty.JettyTransporterConfigurationKeys

public final class JettyTransporterConfigurationKeys extends Object
Configuration for Jetty Transport.
Since:
2.0.1
  • Field Details

    • CONFIG_PROP_FOLLOW_REDIRECTS

      Deprecated.
      Use ConfigurationProperties.HTTP_REDIRECT_MODE instead.
      If enabled, Jetty client will follow HTTP redirects.
      See Also:
      Sourced from:
      RepositorySystemSession.getConfigProperties()
      Value type:
      Boolean
      Default value:
      DEFAULT_FOLLOW_REDIRECTS
      Supports Repo ID Suffix:
      Yes
    • DEFAULT_FOLLOW_REDIRECTS

      public static final boolean DEFAULT_FOLLOW_REDIRECTS
      See Also:
    • CONFIG_PROP_MAX_REDIRECTS

      public static final String CONFIG_PROP_MAX_REDIRECTS
      The max redirect count to follow.
      See Also:
      Sourced from:
      RepositorySystemSession.getConfigProperties()
      Value type:
      Integer
      Default value:
      DEFAULT_MAX_REDIRECTS
      Supports Repo ID Suffix:
      Yes
    • DEFAULT_MAX_REDIRECTS

      public static final int DEFAULT_MAX_REDIRECTS
      See Also:
    • CONFIG_PROP_FOLLOW_INSECURE_REDIRECTS

      Deprecated.
      Use ConfigurationProperties.HTTP_FOLLOW_INSECURE_REDIRECT instead.
      If enabled, Jetty client will follow redirects that downgrade the protocol from https to http. Disabled by default: such a downgrade strips transport encryption from artifact and checksum bytes and makes repository credentials eligible for transmission over plaintext, so a downgrading redirect fails the transfer instead.
      Since:
      2.0.23
      See Also:
      Sourced from:
      RepositorySystemSession.getConfigProperties()
      Value type:
      Boolean
      Default value:
      DEFAULT_FOLLOW_INSECURE_REDIRECTS
      Supports Repo ID Suffix:
      Yes
    • DEFAULT_FOLLOW_INSECURE_REDIRECTS

      @Deprecated public static final boolean DEFAULT_FOLLOW_INSECURE_REDIRECTS
      Deprecated.
      Use ConfigurationProperties.DEFAULT_HTTP_FOLLOW_INSECURE_REDIRECT instead.
      See Also:
    • CONFIG_PROP_ORIGIN_SCOPED_HEADERS

      Deprecated.
      Use ConfigurationProperties.HTTP_ORIGIN_SCOPED_HEADERS instead.
      If enabled (default), operator-configured request headers (aether.transport.http.headers) and preemptively applied Authorization are only sent on requests targeting the repository origin (the scheme, host and port the repository URL denotes). Jetty's redirector copies the request headers onto every redirect hop it follows, so without origin scoping a cross-origin redirect replays the configured headers - which frequently carry credentials such as Authorization or private token headers - to the redirect target host. Disable only when a redirect target legitimately requires the configured headers.
      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

      @Deprecated public static final boolean DEFAULT_ORIGIN_SCOPED_HEADERS
      Deprecated.
      Use ConfigurationProperties.DEFAULT_HTTP_ORIGIN_SCOPED_HEADERS instead.
      See Also: