HTTP Client Attributes
Rod Widdowson
rdw at steadingsoftware.com
Thu May 3 11:11:51 EDT 2018
> OTOH, the following attributes are absent from
> FileBackedHTTPMetadataProvider but present on
> DynamicHTTPMetadataProvider:
>
> supportedContentTypes
> disregardSslCertificate (DEPRECATED)
> maxConnectionsTotal
> maxConnectionsPerRoute
>
> That seems to be an oversight. Can someone confirm the following?
>
> 1. The latter four attributes apply to FileBackedHTTPMetadataProvider as well.
>From the schema:
supportedContentTypes,
maxConnectionsTotal,
maxConnectionsTotal
are *NOT* available (directly) on the batch loaders.
disregardSslCertificate
is deprecated and its status is irrelevant.
> 2. The latter three attributes are incompatible with httpClientRef.
>From the code: The following attributes cause a warning to be emitted if present with a httpClientRef
requestTimeout
connectionTimeout
connectionRequestTimeout
socketTimeout
disregardSslCertificate
disregardTLSCertificate
proxyHost
proxyPort
proxyUser
proxyPassword
> 3. The supportedContentTypes attribute is independent of httpClientRef.
Entirely. The content type is checked after the client has been used to get the response.
HTH
/Rod
More information about the dev
mailing list