Does not use gzip about 123done

[lloyd]

perhaps this is something we should build directly into the reverse proxy in awsbox?

On Oct 12, 2012, at 12:03 AM, Francois Marier [email protected] wrote:

http://www.webpagetest.org/result/121010_P6_8HF/1/performance_optimization/#compress_text

—
Reply to this email directly or view it on GitHub.

[fmarier]

@lloyd excellent point. I had a quick look at the awsbox code, but it looks like it might be part of the AMI and I couldn't find out how you build those.

So I've opened an awsbox bug for this: https://github.com/lloyd/awsbox/issues/37

[lloyd]

It is part of the ami.

lloyd/awsbox-proxy-server is the source code that maps into ~proxy in the AMI. That little tiny reverse proxy is what would need to be hacked to magically support gzip. If you were interested in hacking, you could deploy a box, hack on ~proxy, then push to a fork of awsbox-proxy-server and I could spin a new AMI with the code.

Otherwise, an issue works.

On Oct 14, 2012, at 6:55 PM, Francois Marier [email protected] wrote:

@lloyd excellent point. I had a quick look at the awsbox code, but it looks like it might be part of the AMI and I couldn't find out how you build those.

So I've opened an awsbox bug for this: lloyd/awsbox#37

—
Reply to this email directly or view it on GitHub.

[Lennie]

(I don't know what the architecture looks like but:)

Have you considered just using something like nginx to handle SSL, gzip and maybe static files ? In the future it could also handle SPDY and/or OCSP stapling (both are now beta features of nginx).