Not respecting max-age: 0 for Cache-Control

[kingargyle]

For some reason even if I put a addRequestProptery("Cache-Control", "max-age: 0") on a connection, the HttpResponseCache is always returning the cached data. If I disable the HttpResponseCache completely, then the most current data is always returned.

I checked the headers being returned using Chrome and the Response headers are setting the max-age headers with a value of zero.

Is there a way to ignore the cache during a particular connection, particularly if you are doing a put or a get with a parameter that may do updates?

[lkorth]

If you take a look at Google's documentation they have exactly what you're looking for.

Force a Network Response

In some situations, such as after a user clicks a 'refresh' button, it may be necessary to skip the cache, and fetch data directly from the server. To force a full refresh, add the no-cache directive:

connection.addRequestProperty("Cache-Control", "no-cache");

If it is only necessary to force a cached response to be validated by the server, use the more efficient max-age=0 instead:

   connection.addRequestProperty("Cache-Control", "max-age=0");