HTTP Client Attributes
Tom Scavo
trscavo at gmail.com
Thu May 3 14:10:57 EDT 2018
On Thu, May 3, 2018 at 2:05 PM, Brent Putman <putmanb at georgetown.edu> wrote:
>
> On 5/3/18 1:46 PM, Tom Scavo wrote:
>
> - 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.
What happens if httpCaching is set to "none" on DynamicHTTPMetadataProvider?
> - 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.
Hmm, okay, then the docs are wrong. I'll fix that eventually (unless
you beat me to it).
Tom
More information about the dev
mailing list