A couple of closing-out notes from our vantage point in Massachusetts. First, even though the cache for one of our files was not supposed to expire until June 5, it was serving the correct content as of late June 3. Whether it was an ISP issue or a GFE issue, we will never know.
Second, we have deployed the technique recommended by Donovan and hope to never see this problem again. Finally, a bouquet of virtual flowers for Ikai. Thanks for jumping on the problem and helping us put a solution in place. On Jun 3, 7:43 pm, Tim Hoffman <[email protected]> wrote: > Hi Ikae > > We couldn't leave the production environment in place with the broken > urls. > So have already deployed a version with args on the end of all css/js > urls. > > I don't believe it was an ISP issue. We tried accessing the site > from 5 different ISP's in Australia when we first discovered the > problem. > > Maybe you behind googles infrastructure can't see the issue. More than > a few people have posted > links exhibiting the problem in the list (and they aren't in > Australia). > > We have a full test instance in gae as well but we haven't been > mapping it do a domain to date. > As we have never experienced this issue before. (Site went live mid > last yearwww.polytechnic.wa.edu.au) > > Rgds > > T > > On Jun 4, 1:49 am, "Ikai L (Google)" <[email protected]> wrote: > > > > > Tim, can you provide 2 URLs that are doing this? > > > I'm still trying to reproduce the problem. Could an ISP be caching these > > files? > > > On Thu, Jun 3, 2010 at 10:02 AM, Tim Hoffman <[email protected]> wrote: > > > Hi > > > > Not to bad an idea. > > > > At the moment all of our templates use '/css/some_file.css' > > > rather than including hosts. So we don't need to make changes between > > > code bases > > > or have to lookup what the host should be, (in light of the issue we > > > may well have to change that strategy) > > > > For the moment we just add ?<some value> to the end of the css/js > > > files that are changing, and will probably set up a script to be run > > > prior to appcfg, to increment > > > these values. All the css/js is referenced in just a couple of main > > > templates (zpt) > > > > Rgds > > > > T > > > > On Jun 3, 10:17 pm, J <[email protected]> wrote: > > > > Tim, what we ended up doing was a bit different. We have qa.abc.com > > > > pointing to xyz-qa.appspot.com. > > > > > We did not change file names as was recommended -- that would be a > > > > pain in the rear to manage. But we took advantage of the fact that xyz- > > > > qa.appspot.com delivers content correctly. We changed references to / > > > > scripts/pqr.js tohttp://xyz-qa/appspot.com/scripts/pqr.js. > > > > > It was faster to put in place and it buys us some time until we can > > > > come up with something better. > > > > > Hope that helps. > > > > > On Jun 2, 7:44 pm, Tim Hoffman <[email protected]> wrote: > > > > > > Hi > > > > > > I have raised an issue for this > > > > > >http://code.google.com/p/googleappengine/issues/detail?id=3297 > > > > > > Rgds > > > > > > T > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Google App Engine" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<google-appengine%2Bunsubscrib > > > [email protected]> > > > . > > > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
