There could be an overzealous cache somewhere in the middle - either intentionally, or misconfigured, or an old buggy version.
For example: http://squid-web-proxy-cache.1019090.n4.nabble.com/Problem-with-cached-entries-w-ETag-and-request-without-If-None-Match-header-td1048627.html I also vaguely recall a mention of overzealous caching in the nginx wiki (probably under Expires or ETag)... -- K 2012/11/2 Keith Wiley <kbwi...@gmail.com> > I haven't considered testing different kinds of connections...I figured > the phone was responsible for the caching and the issue was unrelated to > the connection...but I could test it. For that matter, it could be the > fault of the particular phone (perhaps this phone caches http data without > "permission"). At the current time, most of my tests have been performed > over cell, not wifi (TMobile, Seattle area if that matters). > > > On Friday, November 2, 2012 8:01:15 AM UTC-7, Robert Greenwalt wrote: >> >> Even if this is a carrier issue, please let us know - we'd like the >> carriers to do the right thing and do have some contacts to explore issues >> like this. >> >> Kieth, was this on mobile data or on wifi (or other)? >> >> -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
