HTTP Client Attributes

[Brent Putman]

On 5/3/18 11:50 AM, Cantor, Scott 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

That's true, the HTTP batch ones cache ETag and Last-Modified, so they
can do conditional GETs.  They don't however cache the actual response
data, so it's a little different than HttpClient "native" memory or
disk caching.

> We didn't need the HttpClient's support for the batch case.
Yes.  It probably also makes less sense to do for batch since the files
are very large and you probably on average request/refresh them less
often than you would with dynamic, where you have lots of smaller files
that you might want to (re)fetch more frequently.  But it's an option
if people want it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20180503/db871a6d/attachment.html>