HTTP Client Attributes

Brent Putman putmanb at georgetown.edu
Thu May 3 14:05:33 EDT 2018



On 5/3/18 1:46 PM, Tom Scavo wrote:
>
> Based on everything I've read and heard so far, here is what I think
> is going on:
>
> - By default, the HTTP metadata providers perform HTTP conditional GET
> but they do not cache the response body, and moreover, the cached HTTP
> headers do not survive a restart.
Yes, for the batch ones.  The dynamic HTTP one does not cache the
conditional GET headers internally, it delegates both conditional GET
and response body caching to the HttpClient caching layer, and for that
it defaults to 'memory'.  As the docs say.
>
> - To cache the full HTTP response (including the response body) set
> the httpCaching attribute to either “file” or “memory”.

Yes.

> - The full HTTP response will survive a restart if (and only if)
> httpCaching=”file”.

No, 'file' doesn't survive restarts.  The point of that is disk-based
caching to eliminate memory usage, not to be persistent across restarts.

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


More information about the dev mailing list