Changing the Cache-Control to just "public" in addition to adding Expires does seem to work when I use wget to test. Thanks! I'll give it some time to see if the logs look differently on the requests.
On Feb 9, 8:18 am, David <[email protected]> wrote: > I just tried adding Expires and Date headers and that doesn't work > either. > > On Feb 8, 4:52 am, Joshua Smith <[email protected]> wrote: > > > Have you tried using: > > self.response.headers["Cache-Control"] = "public" > > self.response.headers["Expires"] = …some code to generate a time > > stamp... > > > On Feb 7, 2011, at 11:03 PM, David wrote: > > > > I understand the cache hits aren't guaranteed, but I've yet to see any > > > cache hits though. I have about 9000 url hits in the dashboard in the > > > past 2 hours since the maintenance for the url that returns "Cache- > > > Control", "public; max-age=1800;". It seems to me like it's not > > > caching it at all. I'm just trying to reduce that number to something > > > a lot less even though it might not be perfect. Any help would be > > > appreciated. > > > Thanks, > > > David > > > > On Feb 2, 3:39 pm, "Ikai Lan (Google)" <[email protected]> > > > wrote: > > >> Hey guys, > > > >> A few things about the cache-control headers: > > > >> - We do not guarantee your responses will be cached. We make a best > > >> effort > > >> to do caching, but at best, this is an optimization. In the worst case > > >> scenario all requests will continue to reach your app > > > >> - You *may* hit a different edge cache than your original one, which may > > >> contain different data. I don't believe this is happening in your case, > > >> but > > >> it would explain cache inconsistencies with short lived caches (user hits > > >> once cache, subsequent request gets a cache with slightly older data. > > >> This > > >> is rare) > > > >> -- > > >> Ikai Lan > > >> Developer Programs Engineer, Google App Engine > > >> Blogger:http://googleappengine.blogspot.com > > >> Reddit:http://www.reddit.com/r/appengine > > >> Twitter:http://twitter.com/app_engine > > > >> On Wed, Feb 2, 2011 at 1:45 PM, Brandon Wirtz <[email protected]> > > >> wrote: > > >>> Didn't see any change after setting to public. > > > >>> -----Original Message----- > > >>> From: [email protected] > > >>> [mailto:[email protected]] On Behalf Of Brandon Wirtz > > >>> Sent: Wednesday, February 02, 2011 12:48 PM > > >>> To: [email protected] > > >>> Subject: RE: [google-appengine] Cache headers not working w/ billing > > >>> enabled > > > >>> Just made the change... I'll check back to see if it helps. > > > >>> It doesn't appear I can set the cache header for files served from > > >>> static... > > >>> Am I missing something some where? > > > >>> -----Original Message----- > > >>> From: [email protected] > > >>> [mailto:[email protected]] On Behalf Of Robert Kluin > > >>> Sent: Wednesday, February 02, 2011 10:18 AM > > >>> To: [email protected] > > >>> Subject: Re: [google-appengine] Cache headers not working w/ billing > > >>> enabled > > > >>> Hi Brandon, > > >>> Have you tried setting 'cache-control: public; max-age=300'? Note > > >>> 'public.' > > > >>> Robert > > > >>> On Wed, Feb 2, 2011 at 03:43, Brandon Wirtz <[email protected]> wrote: > > >>>> I didn't know this was supposed to work... My app does the same > > >>>> thing... > > >>>> Edge Caching doesn't seem to be happening. > > > >>>> This implies it should... > > >>>>https://groups.google.com/group/google-appengine/browse_thread/thread/ > > >>>> f10804 > > >>>> 5013a2345c?pli=1 > > > >>>> but my app does the same thing yours does, and > > >>>>http://www.seoconsultants.com/tools/headersverifiedmyheaders were > > >>>> set right. > > > >>>> #1 Server Response:http://www.xyhd.tv/aboutHTTPStatusCode: > > >>>> HTTP/1.1 200 OK > > >>>> via: HTTP/1.1 GWA > > >>>> x-powered-by: PHP/5.2.14 > > >>>> vary: Accept-Encoding > > >>>> location:http://wp.xyhd.tv/about/ > > >>>> content-type: text/html; charset=UTF-8 > > >>>> x-pingback:http://wp.xyhd.tv/xmlrpc.php > > >>>> cache-control: max-age=300 > > >>>> Date: Wed, 02 Feb 2011 08:41:03 GMT > > >>>> Server: Google Frontend > > >>>> Content-Length: 0 > > > >>>> And thanks for pointing this out, It caused me to find a bug in my > > >>>> code that I'm not cleaning up headers in my app so the "location" > > >>>> shows wrong. Which might create some weirdness for me. > > > >>>> -----Original Message----- > > >>>> From: [email protected] > > >>>> [mailto:[email protected]] On Behalf Of David > > >>>> Sent: Tuesday, February 01, 2011 8:01 AM > > >>>> To: Google App Engine > > >>>> Subject: [google-appengine] Cache headers not working w/ billing > > >>>> enabled > > > >>>> I have billing enabled on my app and I'm trying to get the Cache- > > >>>> control headers to edge cache a page. I'm setting the header to > > >>>> Cache- > > >>>> Control: public; max-age=300; and I see it coming back. I'm using > > >>>> wget to test it out. I've also included a "now" date in the generated > > >>>> document so I can see if it's caching it or not. It is generating > > >>>> that now date with every request and I see logs coming in on the > > >>>> dashboard as 200. Am I doing something wrong? How do I get server > > >>>> side > > >>> caching working? > > > >>>> Thanks, > > >>>> David > > > >>>> Here is the output from my wget call: > > > >>>> ---request begin--- > > >>>> GET /v2/config HTTP/1.0 > > >>>> User-Agent: Wget/1.12 (cygwin) > > >>>> Accept: */* > > >>>> Host: 11.latest.word-play.appspot.com > > >>>> Connection: Keep-Alive > > > >>>> ---request end--- > > >>>> HTTP request sent, awaiting response... > > >>>> ---response begin--- > > >>>> HTTP/1.0 200 OK > > >>>> Content-Type: application/json; charset=ISO-8859-1 > > >>>> Cache-Control: public; max-age=300; > > >>>> Date: Tue, 01 Feb 2011 15:52:10 GMT > > >>>> Server: Google Frontend > > > >>>> ---response end--- > > >>>> 200 OK > > >>>> URI content encoding = `ISO-8859-1' > > >>>> Length: unspecified [application/json] Saving to: `STDOUT' > > > >>>> -- > > >>>> 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%[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%[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%[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%[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%[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]. > > > For more options, visit this group > > > athttp://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]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
