For HTML files, I would caution against setting such a large default_expiration value (7 days).
Setting it to such a high value means that, worst case, if you decide to change one of your site's pages, end users won't be able to see the change for 7 days (due to caches at both the browser level and Google's edge cache servers). You can get away with leaving a large default_expiration value for all other static files (eg. CSS, JS, images) and still have new static file uploads appear "instantly" by versioning them (eg. base1.css, base2.css). Nick On 20 June 2012 01:50, Andreas <[email protected]> wrote: > christofer that does not make sense. he has only static html so static > file handlers will do all he needs. > why setting up a handler for this anyway? single or multithreaded... > static file handlers are the best choice in this case. > > On Jun 19, 2012, at 11:45 AM, Christopher Ramírez wrote: > > It's better for you to use python27 since it is multithreaded. That's > means an instance can handle more than one request simustaneously. Also > increase "default_expiration" when you be ready to deploy to the public > your website. default_expiration: "7d" (7 days) is a good value. > > On Tuesday, June 19, 2012 3:48:10 AM UTC-6, Apra Barua wrote: >> >> Hey, I got it to work, it is not creating instance now. Thanks. The >> following app.yaml file worked. >> >> application: myappname >> version: 1 >> runtime: python >> api_version: 1 >> >> default_expiration: "12m" >> >> handlers: >> - url: /(.*\.(gif|png|jpg|ico|js|css|**pdf|html)) >> static_files: \1 >> upload: (.*\.(gif|png|jpg|ico|js|css|**pdf|html)) >> >> - url: / >> static_files: index.html >> upload: index.html >> >> >> On Monday, June 18, 2012 10:08:32 PM UTC+5:30, Kyle Finley wrote: >>> >>> Have you mapped the root ('/') to a template? If so, App Engine will >>> have to start an instance to handle this request. Also any request that are >>> not specified in the app.yaml file will be sent to the instance causing it >>> to start up. Be sure to account map the *favicon.icon* for example. >>> >>> Generally I would not worry about it consuming frontend instance hours >>> unless your site is geting more then 1 or 2 request / sec. App Engine >>> graciously gives you 28hrs / day more then enough to fulfill 1 to 2 request >>> / sec. >>> >>> If you still have questions post your app.yaml file so we'll have a >>> better idea of your set up. >>> >>> - Kyle >>> >>> >>> > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/5sR8SAHUfGoJ. > 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. > > > -- > 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. > -- 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.
