I am glad you found a fix. But doesn't this raise a red flag? It sounds like a band-aid, a kludge, a temporary fix rather than an industrial strenght solution. After all: it means that that GET request will not be cached by ANY agent along the chain. That sounds rather draconian, unless you are 100% positive no one will ever do the same GET request twice, expecting the same data.
Of course, if the proper fix has to be implemented either at the origin server or the proxy (and you have no control over these), you may have to make the "temporary fix" permanent anyway. On Jul 12, 12:58 am, Nikolay Elenkov <[email protected]> wrote: > On Tue, Jul 12, 2011 at 11:56 AM, Nikolay Elenkov > > <[email protected]> wrote: > > On Mon, Jul 11, 2011 at 9:15 PM, Streets Of Boston > > <[email protected]> wrote: > >> Wild guess... and i could be totally wrong: It could be a proxy returning > >> an > >> empty result for some reason. > >> Try to set the HTTP caching headers in the request to no-cache: > >> Cache-Control: no-cache > >> and > >> Pragma: no-cache > > > Thanks for idea. It's mostly GET's to a cgi, so you might well be right. > > Will try it out. > > Seems that was exactly the problem. Setting the no cache headers fixed it. > Thank you! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
