HTTP Client Attributes

Tom Scavo trscavo at gmail.com
Thu May 3 11:56:22 EDT 2018


On Thu, May 3, 2018 at 11:44 AM, Brent Putman <putmanb at georgetown.edu> wrote:
>
> On 5/3/18 11:24 AM, Tom Scavo wrote:
>
> On Thu, May 3, 2018 at 11:11 AM, Rod Widdowson <rdw at steadingsoftware.com>
> wrote:
>
> From the schema:
>         supportedContentTypes,
>         maxConnectionsTotal,
>         maxConnectionsTotal
>                 are *NOT* available (directly) on the batch loaders.
>
> That seems like a bug. Should I file an issue in jira?
>
> No.  The maxConnections* ones are not relevant to t he batch HTTP providers,
> since they only ever execute 1 HTTP connection at a time, to the domain they
> are configured with.  The dynamic provider can have many simultaneous
> connections, to many different mains (routes).

Okay, I see. Are the maxConnections* attributes mutually exclusive of
the httpClientRef attribute?

> The supportedContentTypes option is simply not supported by the (older)
> batch resolvers.

For historical reasons, not technical reasons, I presume.

> Hmm, the wiki docs do not agree with the above list so let me ask: Are
> basicAuthUser and basicAuthPassword mutually exclusive of
> httpClientRef? Are httpClientRef and httpClientSecurityParametersRef
> mutually exclusive of each other?
>
> Off-hand I don't remember for sure. I'd have to look.  I didn't think they
> were.

Thanks Brent.

Tom


More information about the dev mailing list