The nginx docs here note that gzip_http_version defaults to 1.1: http://wiki.nginx.org/HttpGzipModule#gzip_http_version
Which might explain the behavior on Heroku. And this blog post mentions nginx config for using CloudFront, specifically setting gzip_http_version to 1.0: http://www.nomitor.com/blog/2010/11/10/gzip-support-for-amazon-web-services-cloudfront/ Rob On Apr 27, 4:27 am, Rob <da...@coaster.com> wrote: > It seems like Heroku's nginx may be set to issue a gzipped response > only for HTTP/1.1 requests. In my quick tests, a 1.0 request with an > "Accept-Encoding: deflate, gzip" header gets an uncompressed response, > but the same request under 1.1 gets gzipped content. > > Unfortunately, Amazon CloudFront, which otherwise functions nicely as > an origin-pull CDN, always issues 1.0 requests, which may explain why > it won't seem to serve gzipped content for my Heroku app. > > Has anyone else seen the same results? > Rob -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
