Our ISP is Verizon. Here are the TraceRoutes:
C:\Users\Jitendra>tracert qa.connectscholar.com Tracing route to ghs.l.google.com [74.125.113.121] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 7 ms 6 ms 7 ms L100.BSTNMA-VFTTP-86.verizon-gni.net [98.110.150.1] 3 9 ms 9 ms 7 ms G1-0-786.BSTNMA-LCR-07.verizon-gni.net [130.81.110.244] 4 12 ms 10 ms 11 ms so-0-3-0-0.BOS-BB-RTR1.verizon-gni.net [130.81.29.252] 5 22 ms 20 ms 21 ms so-9-1-0-0.NY325-BB-RTR1.verizon- gni.net [130.81.19.70] 6 89 ms 19 ms 18 ms 0.so-0-0-0.XL3.NYC4.ALTER.NET [152.63.1.41] 7 17 ms 19 ms 18 ms 0.xe-5-0-0.BR3.NYC4.ALTER.NET [152.63.16.181] 8 22 ms 19 ms 19 ms te-7-0-0.edge2.NewYork2.level3.net [4.68.110.69] 9 19 ms 18 ms 19 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222] 10 31 ms 28 ms 29 ms ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89] 11 38 ms 34 ms 36 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.158] 12 27 ms 25 ms 26 ms ae-4-99.edge1.Washington1.Level3.net [4.68.17.208] 13 28 ms 29 ms 83 ms GOOGLE- INC.edge1.Washington1.Level3.net [4.79.231.6] 14 28 ms 26 ms 26 ms 209.85.241.50 15 39 ms 39 ms 59 ms 209.85.248.75 16 55 ms 56 ms 55 ms 209.85.243.25 17 55 ms 54 ms 53 ms 209.85.251.228 18 55 ms * * 72.14.236.193 19 56 ms 55 ms 54 ms vw-in-f121.1e100.net [74.125.113.121] Trace complete. C:\Users\Jitendra>tracert charityaxis-qa.appspot.com Tracing route to appspot.l.google.com [72.14.204.141] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 8 ms 6 ms 6 ms L100.BSTNMA-VFTTP-86.verizon-gni.net [98.110.150.1] 3 11 ms 10 ms 10 ms G1-0-786.BSTNMA-LCR-07.verizon-gni.net [130.81.110.244] 4 10 ms 11 ms 11 ms so-0-3-0-0.BOS-BB-RTR1.verizon-gni.net [130.81.29.252] 5 20 ms 19 ms 19 ms so-9-1-0-0.NY325-BB-RTR1.verizon- gni.net [130.81.19.70] 6 17 ms 18 ms 19 ms 0.so-0-0-0.XL3.NYC4.ALTER.NET [152.63.1.41] 7 20 ms 69 ms 21 ms 0.xe-5-0-0.BR2.NYC4.ALTER.NET [152.63.18.5] 8 17 ms 18 ms 18 ms xe-10-2-0.edge2.NewYork2.level3.net [4.68.110.233] 9 19 ms 18 ms 18 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222] 10 29 ms 27 ms 28 ms ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89] 11 36 ms 36 ms 26 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.158] 12 30 ms 32 ms 26 ms ae-3-89.edge1.Washington1.Level3.net [4.68.17.144] 13 28 ms 29 ms 28 ms GOOGLE- INC.edge1.Washington1.Level3.net [4.79.22.38] 14 30 ms 30 ms 31 ms 209.85.240.136 15 36 ms 31 ms 35 ms 66.249.94.54 16 29 ms 28 ms 26 ms iad04s01-in-f141.1e100.net [72.14.204.141] Trace complete. C:\Users\Jitendra> On Jun 4, 6:23 pm, "Ikai L (Google)" <[email protected]> wrote: > Can you guys run a traceroute on your domains vs. the appspot domain? > > E.g: > > traceroute qa.connectscholar.com > traceroute charityaxis-qa.appspot.com > > If you're on Windows, the equivalent command is "tracert". > > I'm curious if there's an ISP or specific Google Frontend that is acting up. > > On Thu, Jun 3, 2010 at 2:02 PM, Ikai L (Google) <[email protected]> wrote: > > > > > You should still be billed for bandwidth. The advantage of using edge > > caching is that if the resource is being served from the datastore or > > dynamically generated via some other means, you will not incur CPU costs. > > > On Thu, Jun 3, 2010 at 12:55 PM, Ross M Karchner > > <[email protected]>wrote: > > >> Partially off-topic--- if GFE serves a cached resource, do we get billed > >> for the bandwidth? > > >> On Wed, Jun 2, 2010 at 3:27 PM, Ikai L (Google) <[email protected]>wrote: > > >>> 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 <[email protected]> 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)" <[email protected]> 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 <[email protected] > >>>> >wrote: > > >>>> > > On Wed, Jun 2, 2010 at 3:37 PM, J <[email protected]> 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)" <[email protected]> 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 <[email protected]> > >>>> 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 <[email protected]> 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 > >>>> > > [email protected]. > >>>> > > >> > To unsubscribe from this group, send email to > >>>> > > >> > [email protected]<google-appengine%2Bunsubscrib > >>>> > > >> > [email protected]><google-appengine%2Bunsubscrib > >>>> [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]<google-appengine%2Bunsubscrib > >>>> > > [email protected]><google-appengine%2Bunsubscrib > >>>> [email protected]> > >>>> > > . > >>>> > > > 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 > >>>> [email protected]. > >>>> > > To unsubscribe from this group, send email to > >>>> > > [email protected]<google-appengine%2Bunsubscrib > >>>> > > [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]<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]<google-appengine%2Bunsubscrib > >>> [email protected]> > >>> . > >>> For more options, visit this group at > >>>http://groups.google.com/group/google-appengine?hl=en. > > >> -- > >> You received this message because > > ... > > read more » -- 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.
