> Setting the cache control to private will also mean intranets, ISPs > and suchlike won't be caching anymore, which is a situation I would rather > avoid.
So you saying you dont mind all customers of that ISP getting the same stale data, just dont want it for all you users. ? You could just add a changing cache-busting fragment to the URL. Perhaps hashed off the remote IP address. Then you will have say 10 differnt versions stored in Googles cache, and different people (depending on their IP) will get a different version. By the laws of probablity, each version will (or should) get cached at different times on the frontend, so each will update on a different cycle. (but you will also have to be more specific with your expirely time - not just using 00:00. eg using 24 hours from the request time. Or use say 25 hours, so over time the exact refresh time of each 'shard' shifts around) -- 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-appengine@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.
