Re: RE: [google-appengine] HR applications and Cache Control/Pragma/Expires headers
On Sunday, May 15, 2011 2:03:39 AM UTC+1, Brandon Wirtz wrote: And I noticed that SOME Company I won’t name, names…. Every Time they Run an Ad on one of my pages they seem to think they need to send the AD bot, and the Index Bot (twice) to the page, and they always do it with in 3 seconds of the page being requested, so my bill could be like 1/3 what it is if this was fixed… Or maybe that’s the plan…. Are you guys in the GAE team giving the Adsense and Search Teams a Kick back the more they hit my site? Somewhat OT perhaps, but the 2nd largest ISP in the UK has started implementing something that might seem dumb in so many ways (and many suggest is probably illegal) but they revisit EVERY unique non-HTTPS URL that any of their customers visit, duplicating at least all the query params and quite possibly the HTTP headers, typically about a minute after the original visit. http://www.talktalk.co.uk/products/virus-alerts/ They've been trialling this for a year or so, but seem to have turned it on for every customer (there is no opt out for customers) in the last week or so. This could, of course, play havoc with your bills, not to mention the side effects of duplicate calls to REST type APIs - for example twitter.com always complains that I'm double posting messages now, and I was was testing out pubnub.com and it caused all the messages I published to be published twice until they (pubnub) quickly made some changes to fix this. So if you see repeated traffic from a useragent TalkTalk Virus Alerts Scanning Engine or similar (at least they're using a different UserAgent) then that's what it is. It would SEEM that, having been lobbied and nagged, they have bowed to some pressure and are respecting robots.txt at this stage so that's a quick fix for now, but who's to say if they'll continue to do so in the future. There are of course various forums debating the legality, motives, practicalities and intelligence of such a system, and I don't want to drag this forum into any of those avenues (google for StalkStalk if you're interested), but just a friendly warning of something to watch for that could easily be doubling some of your bills for no good reason, and a quick and easy way to check for it and fix it. -- 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 google-appengine@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.
RE: [google-appengine] HR applications and Cache Control/Pragma/Expires headers
Can I bribe somebody to do my apps? (I even moved to 1.5 hoping that'd auto fix them) My apps all return this: HTTP/1.1.200.OK(CR)(LF) Cache-Control:.no-cache,.must-revalidate(CR)(LF) Content-Type:.text/html;.charset=UTF-8(CR)(LF) Set-Cookie:.S=apphosting=JPio4yliHelJf10OZQQWDw;.path=/(CR)(LF) Date:.Sun,.15.May.2011.00:43:02.GMT(CR)(LF) Pragma:.no-cache(CR)(LF) Expires:.Fri,.01.Jan.1990.00:00:00.GMT(CR)(LF) Server:.Google.Frontend(CR)(LF) And I noticed that SOME Company I won't name, names.. Every Time they Run an Ad on one of my pages they seem to think they need to send the AD bot, and the Index Bot (twice) to the page, and they always do it with in 3 seconds of the page being requested, so my bill could be like 1/3 what it is if this was fixed. Or maybe that's the plan.. Are you guys in the GAE team giving the Adsense and Search Teams a Kick back the more they hit my site? Not to mention the messages the Webmasters team constantly send saying you have really short expirations on your CSS and Images speed up your site by setting longer cache lengths for your style sheets, javascript, and images And those people at THAT OTHER search engine the one that kind of rhymes with what 95% of the people who try out for American Idol can't do. They just sent me a message that Setting No Cache in headers is interpreted in a way not dissimilar to 'no-index'. No-cache implies that the information is for onetime use and that the user or bot should not view this information as static. If information doesn't have at least some shelf life there is no reason to index it as it may not be there when future users arrive at the site. You have to give them credit on the amount of logic they put in to their failure to understand that maybe I just want the user to not cache the page so I can track them via the server rather than via javascript analytics. (I don't think they liked or believed my answer). From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Gregory D'alesandre Sent: Wednesday, May 11, 2011 11:10 AM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] HR applications and Cache Control/Pragma/Expires headers If this was an existing app prior to 1.5.0 then it is not fixed yet, 1.5.0 put the fix in but we still need to clean up apps that were created prior to 1.5.0. Hope that helps, Greg On Wed, May 11, 2011 at 10:54 AM, Stephen Johnson onepagewo...@gmail.com wrote: I'm confused. I have an HR app and this is what I see when I look at the headers using Firebug for one of my images. You're saying this should be different? On Wed, May 11, 2011 at 9:36 AM, Francois Masurel f.masu...@gmail.com wrote: What is rather strange is that cache headers work perfectly fine with MS applications. I hope it's not a way to increase billing ;-) I'm personaly concerned as I'm serving most of my image and file contents dynamically from datastore or memcache. -- 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 mailto:google-appengine%2bunsubscr...@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 mailto:google-appengine%2bunsubscr...@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. 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. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
RE: [google-appengine] HR applications and Cache Control/Pragma/Expires headers
I’d +100 this and I don’t +1 anything since Google made it a product and I fear they will come after me…. I agree the lack of cache header on HR is a big issue, since all my CSS and JS files get re-downed every page view which is slowing down my CDN product, but MS has too high of Down Time at the moment. From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Francois Masurel Sent: Wednesday, May 11, 2011 2:03 AM To: google-appengine@googlegroups.com Subject: [google-appengine] HR applications and Cache Control/Pragma/Expires headers As described in the post below, High-Replication instances strip out HTTP cache headers : https://groups.google.com/d/msg/google-appengine/TfRUd0KRaZM/vvDbMGQQQN8J It's in fact the main reason why we haven't moved to HR for the moment. Does anybody at Google know when this will be fixed ? Thanx for your help. François -- 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. 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. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
RE: [google-appengine] HR applications and Cache Control/Pragma/Expires headers
Interesting solution… proxy the HR instance through an MS instance that just changes the headers… Sure it will add 22 cents a gig, but you get the cache headers and HR’s uptime. :-) From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Francois Masurel Sent: Wednesday, May 11, 2011 2:03 AM To: google-appengine@googlegroups.com Subject: [google-appengine] HR applications and Cache Control/Pragma/Expires headers As described in the post below, High-Replication instances strip out HTTP cache headers : https://groups.google.com/d/msg/google-appengine/TfRUd0KRaZM/vvDbMGQQQN8J It's in fact the main reason why we haven't moved to HR for the moment. Does anybody at Google know when this will be fixed ? Thanx for your help. François -- 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. 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. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] HR applications and Cache Control/Pragma/Expires headers
Do you know if there is a bug filed for this, already? On Wed, May 11, 2011 at 2:15 AM, Brandon Wirtz drak...@digerat.com wrote: I’d +100 this and I don’t +1 anything since Google made it a product and I fear they will come after me…. I agree the lack of cache header on HR is a big issue, since all my CSS and JS files get re-downed every page view which is slowing down my CDN product, but MS has too high of Down Time at the moment. *From:* google-appengine@googlegroups.com [mailto: google-appengine@googlegroups.com] *On Behalf Of *Francois Masurel *Sent:* Wednesday, May 11, 2011 2:03 AM *To:* google-appengine@googlegroups.com *Subject:* [google-appengine] HR applications and Cache Control/Pragma/Expires headers As described in the post below, High-Replication instances strip out HTTP cache headers : https://groups.google.com/d/msg/google-appengine/TfRUd0KRaZM/vvDbMGQQQN8J It's in fact the main reason why we haven't moved to HR for the moment. Does anybody at Google know when this will be fixed ? Thanx for your help. François -- 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. 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. 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. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
RE: [google-appengine] HR applications and Cache Control/Pragma/Expires headers
I think there was one (or more), and it was closed “by design” (more than once) it gets fixed it reverts, it gets fixed, it reverts. I can dig up the threads on the topic if need be. Something like “Edge Caching is not guaranteed” Yes but this breaks user caching “that’s not guaranteed either”… *Head Thwak* From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Robert Schuppenies Sent: Wednesday, May 11, 2011 8:21 AM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] HR applications and Cache Control/Pragma/Expires headers Do you know if there is a bug filed for this, already? On Wed, May 11, 2011 at 2:15 AM, Brandon Wirtz drak...@digerat.com wrote: I’d +100 this and I don’t +1 anything since Google made it a product and I fear they will come after me…. I agree the lack of cache header on HR is a big issue, since all my CSS and JS files get re-downed every page view which is slowing down my CDN product, but MS has too high of Down Time at the moment. From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Francois Masurel Sent: Wednesday, May 11, 2011 2:03 AM To: google-appengine@googlegroups.com Subject: [google-appengine] HR applications and Cache Control/Pragma/Expires headers As described in the post below, High-Replication instances strip out HTTP cache headers : https://groups.google.com/d/msg/google-appengine/TfRUd0KRaZM/vvDbMGQQQN8J It's in fact the main reason why we haven't moved to HR for the moment. Does anybody at Google know when this will be fixed ? Thanx for your help. François -- 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. 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 mailto:google-appengine%2bunsubscr...@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. 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. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
RE: [google-appengine] HR applications and Cache Control/Pragma/Expires headers
What is rather strange is that cache headers work perfectly fine with MS applications. I hope it's not a way to increase billing ;-) I'm personaly concerned as I'm serving most of my image and file contents dynamically from datastore or memcache. -- 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. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] HR applications and Cache Control/Pragma/Expires headers
I'm confused. I have an HR app and this is what I see when I look at the headers using Firebug for one of my images. You're saying this should be different? On Wed, May 11, 2011 at 9:36 AM, Francois Masurel f.masu...@gmail.comwrote: What is rather strange is that cache headers work perfectly fine with MS applications. I hope it's not a way to increase billing ;-) I'm personaly concerned as I'm serving most of my image and file contents dynamically from datastore or memcache. -- 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. 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. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. attachment: headers.jpg
Re: [google-appengine] HR applications and Cache Control/Pragma/Expires headers
This was a bug that is fixed for new apps in the 1.5.0 admin console and will be fixed for old apps soon. And don't worry Brandon, we have no intention of going after anyone :) Greg On Wed, May 11, 2011 at 9:12 AM, Brandon Wirtz drak...@digerat.com wrote: I think there was one (or more), and it was closed “by design” (more than once) it gets fixed it reverts, it gets fixed, it reverts. I can dig up the threads on the topic if need be. Something like “Edge Caching is not guaranteed” Yes but this breaks user caching “that’s not guaranteed either”… **Head Thwak** *From:* google-appengine@googlegroups.com [mailto: google-appengine@googlegroups.com] *On Behalf Of *Robert Schuppenies *Sent:* Wednesday, May 11, 2011 8:21 AM *To:* google-appengine@googlegroups.com *Subject:* Re: [google-appengine] HR applications and Cache Control/Pragma/Expires headers Do you know if there is a bug filed for this, already? On Wed, May 11, 2011 at 2:15 AM, Brandon Wirtz drak...@digerat.com wrote: I’d +100 this and I don’t +1 anything since Google made it a product and I fear they will come after me…. I agree the lack of cache header on HR is a big issue, since all my CSS and JS files get re-downed every page view which is slowing down my CDN product, but MS has too high of Down Time at the moment. *From:* google-appengine@googlegroups.com [mailto: google-appengine@googlegroups.com] *On Behalf Of *Francois Masurel *Sent:* Wednesday, May 11, 2011 2:03 AM *To:* google-appengine@googlegroups.com *Subject:* [google-appengine] HR applications and Cache Control/Pragma/Expires headers As described in the post below, High-Replication instances strip out HTTP cache headers : https://groups.google.com/d/msg/google-appengine/TfRUd0KRaZM/vvDbMGQQQN8J It's in fact the main reason why we haven't moved to HR for the moment. Does anybody at Google know when this will be fixed ? Thanx for your help. François -- 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. 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. 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. 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. 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. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] HR applications and Cache Control/Pragma/Expires headers
If this was an existing app prior to 1.5.0 then it is not fixed yet, 1.5.0 put the fix in but we still need to clean up apps that were created prior to 1.5.0. Hope that helps, Greg On Wed, May 11, 2011 at 10:54 AM, Stephen Johnson onepagewo...@gmail.comwrote: I'm confused. I have an HR app and this is what I see when I look at the headers using Firebug for one of my images. You're saying this should be different? On Wed, May 11, 2011 at 9:36 AM, Francois Masurel f.masu...@gmail.comwrote: What is rather strange is that cache headers work perfectly fine with MS applications. I hope it's not a way to increase billing ;-) I'm personaly concerned as I'm serving most of my image and file contents dynamically from datastore or memcache. -- 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. 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. 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. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
