Interesting solution… proxy the HR instance through an MS instance that just changes the headers… Sure it will add 22 cents a gig, but you get the cache headers and HR’s uptime. :-)
From: [email protected] [mailto:[email protected]] On Behalf Of Francois Masurel Sent: Wednesday, May 11, 2011 2:03 AM To: [email protected] Subject: [google-appengine] HR applications and Cache Control/Pragma/Expires headers As described in the post below, High-Replication instances strip out HTTP cache headers : https://groups.google.com/d/msg/google-appengine/TfRUd0KRaZM/vvDbMGQQQN8J It's in fact the main reason why we haven't moved to HR for the moment. Does anybody at Google know when this will be fixed ? Thanx for your help. François -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. 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. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. 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.
