On Monday, July 25, 2011 6:24:19 PM UTC+2, barryhunter wrote: > > > 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? > Exactly!
> 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. > Ingenious, I might go for this to be honest. That or just marking it private and letting some extraneous requests through, I mean how common are organization-wide Web proxies these days anyway? -L -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/aiXEB0rcqW4J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
