That's interesting. The URLFetch service does cache results, but these
should be short-lived. Are you fetching a resource that has cache headers
set?
On Thu, Jun 10, 2010 at 6:48 PM, mar_novice mariocape1...@gmail.com wrote:
How quickly? Not that fast. I'm still testing my app and upon
Ooopppss.. my mistake, im looking at an old version of my app. I think
setting the headers with no-cache is enough and no need for the
timestamp.
On Jun 11, 6:27 pm, mar_novice mariocape1...@gmail.com wrote:
Unfortunately, even using
URL urlObj = new URL(url);
HttpURLConnection
I had the same problem. I solved with:
...
URL urlObj = new URL(url);
HttpURLConnection connection = (HttpURLConnection)
urlObj.openConnection();
connection.addRequestProperty(Cache-Control, no-cache,max-age=0);
connection.addRequestProperty(Pragma, no-cache);
...
fabrizio
On Jun 9, 2:29 pm,
How quickly? Not that fast. I'm still testing my app and upon
refreshing the page, sometimes what I get are the cached results. I
even get sometimes the result that was supposed to be yesterday's
result, meaning, a day old result. Can you somehow explain how the
urlfetchservice cache works
