When you say the resource must be revalidatable in the current version, does that mean my resource server must successfully respond with a 304?
And thanks for the confirmation, Jon, regarding the build in support. I'll play around with this and see how it goes. sam On Fri, Jun 7, 2013 at 10:25 AM, Francois-Xavier Bonnet < [email protected]> wrote: > Yes, CachingHttpClient supports this. You can add the header in the > request and CachingHttpClient will send the cached version instead of the > error page even if the cache entry is stale. For example: > Cache-Control: stale-if-error=1200 > But the resource must be cacheable in the first place. In addition the > resource must also be revalidatable (Last-modified or Etag response header > in the response) in current version. > > > > 2013/6/7 <[email protected]> > > No, thanks for the pointer. Does CachingHttpClient support that? >> >> >> On Fri, Jun 7, 2013 at 8:38 AM, Francois-Xavier Bonnet < >> [email protected]> wrote: >> >>> Hello, >>> >>> Did you try stale-if-error request header ? >>> >>> >>> 2013/6/7 Sam Perman <[email protected]> >>> >>>> Hello >>>> >>>> I'm using the CachingHttpClient and have configured a retry handler for >>>> certain types of errors... but what I really want to do is use a >>>> previously >>>> cached response (for certain types of errors) and only retry if there >>>> is no >>>> previously cached response. >>>> >>>> Is this possible? >>>> >>>> thanks >>>> sam >>>> >>> >>> >> >
