Okay, looks like the Google Front-End is kicking in to cache your stuff Server Google Frontend Content-Length 2834 Age 41 Cache-Control public, max-age=600
Are you guys setting this header anywhere? Unfortunately, there's no way to invalidate items in the frontend cache, so you'll have to use a cache buster or wait for the TTL to expire. On Wed, Jun 2, 2010 at 12:22 PM, J <j.si...@earlystageit.com> wrote: > That's interesting, Rafael. I wonder why it serves correctly for you. > > They are still different from my PoV. > > The bad side headers: > Etag "74EQOA" > Date Tue, 01 Jun 2010 18:12:57 GMT > Expires Sat, 05 Jun 2010 02:12:57 GMT > Content-Type text/css > Content-Encoding gzip > Server Google Frontend > Content-Length 2820 > Cache-Control public, max-age=288000 > Age 90134 > X-XSS-Protection 0 > > The good side headers: > Etag "7xGL5w" > Date Wed, 02 Jun 2010 19:13:00 GMT > Expires Wed, 02 Jun 2010 19:12:04 GMT > Content-Type text/css > Content-Encoding gzip > Server Google Frontend > Content-Length 2834 > Age 41 > Cache-Control public, max-age=600 > > Short of using a cache-buster, is there a setting I can use on GAE or > in my app.yaml file? > > On Jun 2, 3:01 pm, "Ikai L (Google)" <ika...@google.com> wrote: > > I wonder if there is some layer of the infrastructure that is performing > > caching without you guys having opted-in, hence the reason why a > > cache-buster like ?v=something works. Can you guys confirm? Also - are > you > > guys setting any headers? Which headers get returned? > > > > I've personally always used cache busters for the simple reason that > > sometimes users using web-accelerators or with aggressive ISP or caching > > settings tend to key off the URL. Can you guys use this workaround in the > > meantime? > > > > On Wed, Jun 2, 2010 at 11:57 AM, Rafael Sierra <rafaeljs...@gmail.com > >wrote: > > > > > > > > > > > > > On Wed, Jun 2, 2010 at 3:37 PM, J <j.si...@earlystageit.com> wrote: > > > > To reproduce the problem, go to > > >http://qa.connectscholar.com/stylesheets/caSkin.css > > > > and also tohttp://charityaxis-qa.appspot.com/stylesheets/caSkin.css. > > > > Both URLs point to the same file but one returns the old content and > > > > appspot.com returns the new content. > > > > > Same file here: > > > > > Hidan:~ sdm$ curlhttp:// > charityaxis-qa.appspot.com/stylesheets/caSkin.css> 1 > > > % Total % Received % Xferd Average Speed Time Time Time > > > Current > > > Dload Upload Total Spent Left > > > Speed > > > 100 10941 0 10941 0 0 6146 0 --:--:-- 0:00:01 > --:--:-- > > > 31918 > > > Hidan:~ sdm$ curlhttp://qa.connectscholar.com/stylesheets/caSkin.css> > 2 > > > % Total % Received % Xferd Average Speed Time Time Time > > > Current > > > Dload Upload Total Spent Left > > > Speed > > > 100 10941 0 10941 0 0 2777 0 --:--:-- 0:00:03 > --:--:-- > > > 3854 > > > Hidan:~ sdm$ md5 1 > > > MD5 (1) = 8f5ef511be1a03fd722223337c334933 > > > Hidan:~ sdm$ md5 2 > > > MD5 (2) = 8f5ef511be1a03fd722223337c334933 > > > > > > On Jun 2, 1:18 pm, "Ikai L (Google)" <ika...@google.com> wrote: > > > >> Thanks for bringing this up, Tim. Anyone else seeing this problem? > If > > > so, > > > >> please post details. Are you guys setting any kind of cache headers? > > > > > >> I'm going to try to reproduce these issues, so any information will > be > > > >> helpful. > > > > > >> On Wed, Jun 2, 2010 at 9:14 AM, J <j.si...@earlystageit.com> wrote: > > > >> > Thanks, Tim, for letting me know I'm not going insane. > > > > > >> > To the Google guys, this problem seems to have started yesterday > > > >> > afternoon (1:30-ish PM, EDT) in case it helps you track down the > > > >> > cause. > > > > > >> > On Jun 2, 8:19 am, Tim Hoffman <zutes...@gmail.com> wrote: > > > >> > > Hi > > > > > >> > > We have been trying to deploy a major revision of one of our > apps. > > > > > >> > > Under the specific version 2-0-0.latest... all the new css/js > and > > > >> > > static images are available. > > > > > >> > > When we make the new version default, the css, js and static > files > > > are > > > >> > > accessible via <appid>.appspot.com > > > > > >> > > However when accessing the same site via the google apps domain > > > >> > > mapping we are still > > > >> > > getting the old versions css, js and static images. > > > > > >> > > I have tried removing the apps domain mapping and re-adding it > with > > > no > > > >> > > affect. > > > > > >> > > We have had to revert to the earlier version as all access to > the > > > site > > > >> > > is via the apps domain and > > > >> > > its not working with the latest version missing the new css/js. > > > > > >> > > has anyone got any ideas on how we can address this. > > > > > >> > > I know absolutely that the problem is not a browser cache, as I > have > > > >> > > been checking the css files via wget. > > > > > >> > > Thanks for any help > > > > > >> > > regards > > > > > >> > > Tim > > > > > >> > -- > > > >> > You received this message because you are subscribed to the Google > > > Groups > > > >> > "Google App Engine" group. > > > >> > To post to this group, send email to > > > google-appeng...@googlegroups.com. > > > >> > To unsubscribe from this group, send email to > > > >> > google-appengine+unsubscr...@googlegroups.com<google-appengine%2bunsubscr...@googlegroups.com><google-appengine%2Bunsubscrib > e...@googlegroups.com><google-appengine%2Bunsubscrib > > > e...@googlegroups.com> > > > >> > . > > > >> > For more options, visit this group at > > > >> >http://groups.google.com/group/google-appengine?hl=en. > > > > > >> -- > > > >> Ikai Lan > > > >> Developer Programs Engineer, Google App Engine > > > >> Blog:http://googleappengine.blogspot.com > > > >> Twitter:http://twitter.com/app_engine > > > >> Reddit:http://www.reddit.com/r/appengine > > > > > > -- > > > > You received this message because you are subscribed to the Google > Groups > > > "Google App Engine" group. > > > > To post to this group, send email to > google-appeng...@googlegroups.com. > > > > To unsubscribe from this group, send email to > > > google-appengine+unsubscr...@googlegroups.com<google-appengine%2bunsubscr...@googlegroups.com><google-appengine%2Bunsubscrib > e...@googlegroups.com> > > > . > > > > For more options, visit this group at > > >http://groups.google.com/group/google-appengine?hl=en. > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Google App Engine" group. > > > To post to this group, send email to google-appengine@googlegroups.com > . > > > To unsubscribe from this group, send email to > > > google-appengine+unsubscr...@googlegroups.com<google-appengine%2bunsubscr...@googlegroups.com><google-appengine%2Bunsubscrib > e...@googlegroups.com> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/google-appengine?hl=en. > > > > -- > > Ikai Lan > > Developer Programs Engineer, Google App Engine > > Blog:http://googleappengine.blogspot.com > > Twitter:http://twitter.com/app_engine > > Reddit:http://www.reddit.com/r/appengine > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appeng...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com<google-appengine%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
