New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
populate ETAG and LAST-MODIFIED for assests #17
Comments
I have now looked into this issue, and there are a number of requirements on the request to make it cachable:
There are a number of exemptions, e.g. only some status codes will cause caching. For instance status code 304 is not cachable. So to make use of the cache status code 200 including the full resource must be served from the application for the resource to be inserted into the cache. When the cache expires the Also some values for the One thing to note is that for App Engine the cache will talk to App Engine and tell which resources was served out of the cache. So even when served from the cache the request will be in the logs in the cloud console. One way to test caching is to have logging in the request handler code, and see that the request is in the log, but the actual request handler is not called. Another way to see that the resource is coming from the cache is that the |
shelf_appengine has been discontinued. |
I can't get caching to work for my assets serviced from the appengine context. Unless there is some magic that is intended to occur in Googles CDN then I imagine the reason is that appengine / shelf_appengine do not populate ETAG and LAST-MODIFIED on the assets
The text was updated successfully, but these errors were encountered: