HTTP Client Attributes

[Brent Putman]

On 5/3/18 11:24 AM, Tom Scavo wrote:
> Thanks Rod. Comments and questions below.
>
> 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).

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

> 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.

>
>
>
> Here is the Million Dollar Question: What is the default value of the
> httpCaching attribute on a FileBackedHTTPMetadataProvider? (Please
> don’t say “none!”)

It is 'none', if one is using the default internally-constructed
HttpClient.  Because of the 1) memory requirements of in-memory and 2)
disk requirements of disk, we didn't want to make assumptions about
either of those defaults being ok.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20180503/12c60b76/attachment.html>