Home/ Questions/Q 8966397
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T17:01:06+00:00

I’m just getting started with my first app engine site. I followed the hello

  • 0

I’m just getting started with my first app engine site. I followed the hello world sample to get my home page up and running. I added a css file and declared a static handler for it in my app.yaml. Here is the full content:

application: myapp
version: 1
runtime: python27
api_version: 1
threadsafe: true

handlers:
- url: /css/.*/(.*)
  mime_type: text/css
  static_files: css/\1
  upload: css/(.*)
  expiration: "30d"

- url: /.*
  script: myapp.app

When I use the Audit feature of the Chrome developer tools, it warns that my CSS file is explicitly non-cacheable. I tried increasing the expiration time, but that didn’t help.

Is there anything else I need to do to enable caching for static files? I haven’t messed around with any settings in the site dashboard, so it should be using the default settings.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    When I run this same test on the SDK against localhost, I get the same warning that none of my CSS is cached and that it’s set to be explicitly non-cachable.

    When I deploy the app and run the test from .appspot.com, I only get a warning for the jquery CDN link, and all of my CSS files are cached.

    Hope this helps.

    EDIT: Looks like the files are marked as proxy-cacheable, but I’m still seeing them as non-browser cacheable.

    • 0