Situation: running a Google App Engine site with my static content's
default_expiration set to "14d"
Problem: in Chrome and Safari, visiting a URL (not reloading, just
putting the cursor in the address bar and hitting Enter), causes a ton
of requests to be fired with If-None-Match headers. The responses are
always 304 Not Modified, as expected. I can watch these requests get
fired in a debugging proxy like Charles or Fiddler.
Want: to avoid these requests and 304 responses entirely for static
content -- simply trust the browser's cached content when it's
available.
We use the standard "cache static content for a really long time,
we'll take care of appending ?version={version} modifications to our
query strings when we need to bust the cache" system, so we'd really
like to avoid the 304's.
Belief: I think this is caused by the etag header that app engine
sends down with every static content response. The app engine SDK does
not send this header down, and I don't see this 304 behavior when
messing around with the SDK.
Any advice? Can you turn off etags for app engine's static content?
Updated with an example piece of static content:
http://www.khanacademy.org/stylesheets/default.css?846.346809036617399050
See a full summary of this question and various responses here:
http://stackoverflow.com/questions/4406651/webkit-etags-and-google-app-engine-caching-behavior
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
