----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/14712/#review27120 -----------------------------------------------------------
Do we really want to not cache all of the REST API requests? I imagine there is some data that is OK to cache. Which APIs specifically are returning you outdated information? - Ryan Baxter On Oct. 17, 2013, 11:48 a.m., Andreas Kohn wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/14712/ > ----------------------------------------------------------- > > (Updated Oct. 17, 2013, 11:48 a.m.) > > > Review request for shindig. > > > Bugs: SHINDIG-1942 > https://issues.apache.org/jira/browse/SHINDIG-1942 > > > Repository: shindig > > > Description > ------- > > We had an issue with IE showing (sometimes) outdated information. In the end > it seems we're hit by some caching issue in IE, as described here: > http://thinking-in-code.blogspot.com/2010/06/preventing-internet-explorer-from.html > > Please note: patch was created against 3.0.0-beta3, but should apply to > 2.5.0-updateX as well. > > > Diffs > ----- > > > tags/shindig-project-3.0.0-beta3/java/common/src/main/java/org/apache/shindig/protocol/DataServiceServlet.java > 1532688 > > tags/shindig-project-3.0.0-beta3/java/common/src/test/java/org/apache/shindig/protocol/DataServiceServletTest.java > 1532688 > > Diff: https://reviews.apache.org/r/14712/diff/ > > > Testing > ------- > > See unit test in patch. > > Issue was observed in our production environment, and was fixed by the patch. > > > Thanks, > > Andreas Kohn > >
