HTTP Client Attributes

[Tom Scavo]

On Thu, May 3, 2018 at 4:40 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 5/3/18, 4:33 PM, "Tom Scavo" <trscavo at gmail.com> wrote:
>
>> And that request will be an HTTP conditional request, right?
>
> No.
>
>> The downside is, when httpCaching="none", it always goes out to the network.
>
> No. There's *no* HTTP caching implemented by the dynamic code, it's left to the client bean. The batch providers have done a limited conditional GET form of caching for a while, independent of the client bean, they just don't physically cache response bodies in the HTTP sense.
>
> The dynamic providers always decide whether to "try to get something new" and if they do, and the back-end is HTTP, then it just asks the client to issue a GET. What happens then is up to the client.

Okay, I think I understand but let me ask: Are the following statements true?

- Regardless of the value of the httpCaching attribute, a
FileBackedHTTPMetadataProvider caches the response headers (but not
the response body) and subsequently performs HTTP conditional GET.

- Regardless of the value of the httpCaching attribute, a
DynamicHTTPMetadataProvider never performs HTTP conditional GET.

Thanks,

Tom