HTTP Client Attributes

[Tom Scavo]

On Thu, May 3, 2018 at 11:50 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:
>> 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.
>
> And because they do their own caching, I believe. I think there was internal logic already to remember a cache tag and use it, just not across restarts (whereas the SP actually stores the cache tags on disk, I think). We didn't need the HttpClient's support for the batch case.

I'm confused. We know that a FileBackedHTTPMetadataProvider does HTTP
caching by default (although I don't know the details). Are you saying
that the HTTP cache attributes (httpCaching, httpCacheDirectory,
httpMaxCacheEntries, httpMaxCacheEntrySize) may be used to override
the default HTTP cache behavior? If so, the default shown in the doc
("none") is incorrect.

Tom