Curiosity got the better of me, and I've just tried this - unfortunately, it doesn't work. When serving from Google Storage using send_blob I received the pre-gzipped content, but the Content-Encoding header was not sent.
You might want to try something with signed URLs ( https://developers.google.com/storage/docs/accesscontrol#Signed-URLs). I've just discovered that the edge cache in front of Google Storage will actually *uncompress* pre-compressed content before serving it (which would mess things up for you), but I suspect this this is a bug, and I also imagine that it won't affect signed URLs. Stephen On Friday, 22 June 2012 12:42:27 UTC+1, Emanuele Ziglioli wrote: > > Thanks for the tip! I will certainly try next week. Storing two versions > would be nice and easy to do! > > On Friday, 22 June 2012 23:38:40 UTC+12, Stephen Lewis wrote: >> >> When you serve up a Cloud Storage object directly from Cloud Storage, you >> can certainly pre-gzip the content and make sure it's served with the >> correct 'Content-Encoding'. The reference to this is at: >> >> >> https://developers.google.com/storage/docs/reference-headers#contentencoding >> >> I'd be interested to know whether this still applies if you serve the >> Cloud Storage object using send_blob in App Engine. I'd imagine it would >> (and should) - it certainly works for Content-Type, because we're already >> using this in one of our apps. >> >> This is, of course, only useful if all your clients understand gzip >> content encoding; if not, you'd probably have to store two version of your >> objects (compressed and uncompressed) and detect which type of client >> you're talking to in your AE code. >> >> If you do try this, please let the rest of us know! >> >> Thanks >> >> Stephen >> >> On Friday, 22 June 2012 12:06:47 UTC+1, Emanuele Ziglioli wrote: >>> >>> thanks for the suggestion. The resources I was talking about are large >>> but not static, that's I've been using compressed entities and now the blob >>> store. >>> Have given up on the blob store for now, and reverted to compressed >>> entities. >>> Might try with the Google cloud store. >>> >>> On Friday, 22 June 2012 18:08:51 UTC+12, Richard Watson wrote: >>>> >>>> As Jeff mentioned on the SDK thread, maybe try Cloudflare.com. I've >>>> just turned it on and it's not too painful, although I had to set up my >>>> page rules just right. If you have static content, they'll gzip and cache >>>> it for you on their CDN. >>>> >>>> One option if you don't want them proxying your whole app: deliver your >>>> content from a different subdomain and tell CF to only proxy that domain. >>>> Then all they are is a DNS host for you. Worth a try at least. >>>> >>>> -- 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/-/CI0O78csAV4J. 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.
