Configuring a file-backed HTTP resource for attribute filters

[Brent Putman]

On 7/21/15 12:51 PM, Cantor, Scott wrote:
> On 7/21/15, 12:35 PM, "users on behalf of Brent Putman" <users-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:
>
>> Well, I haven't been following all the details of this thread, but I think you could get this if you are using a filesystem caching variant of the HttpClient.  There I think the cached data will persist across restarts, so indeed the first fetch after an IdP restart could be doing a conditional GET, if the resource had been fetched and cached previously.  Which HttpClient bean are you using here?
> Ok, admittedly I interpreted "no backup file yet" as equivalent to the file cache not being populated either, which aren't necessarily equivalent. So that is the first question to ask, and one can always flush that directory.

Also just occurred to me that: the Resource impls implement exists(),
which does a fetch from the server.  If that is being called by the
Resource consumer before the actual content is attempted to be
consumed, that 2nd call would result in a cache hit, even on a fresh
restart, because obviously the exists() call would have already
populated the cache.  I think.  That could lead to confusion if the
full log data isn't taken into account.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150721/a2393d3d/attachment.html>