Configuring a file-backed HTTP resource for attribute filters

[Cantor, Scott]

On 7/21/15, 4:56 PM, "users on behalf of Brent Putman" <users-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:

>Ah.  I didn't understand that the 304 you were reporting was from the *web server*.  Not sure anyone else did either.  That is what is expected then.   You should see 1 GET returning a 200, and then more additional GETs returning 304s.  That's normal.

What I assumed from the original message was that *all* he saw was a 304. That's the part I was struggling with until I then assumed the file-based cache was maintained across restarts, but now that apparently isn't true either, so I'm back to confused unless in fact there's both a 200 and a 304.

>In addition to the exists() method I earlier mentioned, there are other methods in HTTPResource which invoke fetches, so those would all result potentially in conditional GETS (what the HttpClient caching subsystem will report as "VALIDATED").

But clearly for a 304 you have to have a primed cache to start with.

-- Scott