Hi Anders, This is strange, because it should set *both* the Expires and the Cache-Control header to be 1 day, and both are wrong.
I attempted to replicate this on one of my applications, but so far have not been able to (for me it's setting both headers correctly). Could you send along your complete app.yaml file and the specific URL on which you are seeing this issue? Thanks, Marzia On Thu, Nov 13, 2008 at 11:38 PM, Anders <[EMAIL PROTECTED]> wrote: > > When the expiration attribute is set in the app.yaml file then the > Cache-Control header still has a max age of 600 seconds. > > For example expiration 1 day in app.yaml: > > - url: /static/images > static_dir: static > expiration: "1d" > > Will result in the response: > > Date: Fri, 14 Nov 2008 07:25:34 GMT > Expires: Fri, 14 Nov 2008 07:35:34 GMT > Cache-Control: public, max-age=600 > Content-Type: image/gif > Server: Google Frontend > Content-Length: 760 > Connection: Close > > Shouldn't the correct max-age for Cache-Control in this case be 86400 > (number of seconds in 1 day)? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
