It works fine with Chrome 7 and Safari 5 on Windows XP in my app, no any requests are sent after the first visiting.
Have you checked the static files if they had an "Expires" header? Also don't enable resource tracking for webkit which will always request for all the resources, just check the background logs. ---------- keakon My blog(Chinese): www.keakon.net Blog source code: https://bitbucket.org/keakon/doodle/ On Wed, Dec 15, 2010 at 9:50 AM, kamens <kam...@gmail.com> wrote: > 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<google-appengine%2bunsubscr...@googlegroups.com> > . > 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 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.
