<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 5/3/18 1:46 PM, Tom Scavo wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAEtu=dPK4-feQ1XcJ20sc2L11YwhRvnEoNWyAYue-qSWDxwVxg@mail.gmail.com"><br>
<pre wrap="">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.</pre>
</blockquote>
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.<br>
<blockquote type="cite"
cite="mid:CAEtu=dPK4-feQ1XcJ20sc2L11YwhRvnEoNWyAYue-qSWDxwVxg@mail.gmail.com">
<pre wrap="">
- To cache the full HTTP response (including the response body) set
the httpCaching attribute to either “file” or “memory”.
</pre>
</blockquote>
<br>
Yes.<br>
<br>
<blockquote type="cite"
cite="mid:CAEtu=dPK4-feQ1XcJ20sc2L11YwhRvnEoNWyAYue-qSWDxwVxg@mail.gmail.com">
<pre wrap="">
- The full HTTP response will survive a restart if (and only if)
httpCaching=”file”.
</pre>
</blockquote>
<br>
No, 'file' doesn't survive restarts. The point of that is
disk-based caching to eliminate memory usage, not to be persistent
across restarts.
<blockquote type="cite"
cite="mid:CAEtu=dPK4-feQ1XcJ20sc2L11YwhRvnEoNWyAYue-qSWDxwVxg@mail.gmail.com"></blockquote>
<br>
</body>
</html>