Configuring a file-backed HTTP resource for attribute filters

[Brent Putman]

On 7/21/15 1:08 PM, Brent Putman wrote:
> Another thing to look at might be the max cache entry size:  We have
> for the FileCachingHttpClient default of:
>
> p:maxCacheEntrySize="%{idp.httpclient.filecaching.maxCacheEntrySize:10485760}
>
> so 10MB.  Could the resource being fetched here be bigger than that?
> I have thought that if the resource is bigger, it simply isn't cached,

Some quick testing against the InCommon metadata seems to indicate that
that is the case.  In this case, responses are not cached, and
subsequent requests result in a CACHE_MISS and another request to the
server, as expected.

With a max cache entry size greater than the resource size, the first
request results in a 200 and CACHE_MISS (as expected), and the second
and subsequent requests result in a 200 and VALIDATED, which is defined as:

    /** The response was generated from the cache after validating the
     * entry with the origin server.
     */

So that aspect all seems as expected.


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