-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gzip #138
Comments
I guess this could be as simple as including the compression module: https://github.com/expressjs/compression |
Well I want gzip also on compiled views and css and js files during packaging. We already use |
So what's the idea for the CSS/JS. If we gzip it and throw it onto the CDN during publish, how do we reference it in the browser? How do we tell the CDN to transfer the content with the correct type? |
So, in theory we reference it in the same way and we publish it in the same way using the usual |
"You also need to develop your application to intercept viewer requests and change the request URL based on whether the request includes an Accept-Encoding: gzip header." For requesting the template, that would probably be OK, the registry can just say 'if the client supports gzip then add the .gz extension to the template path'. But for static css/js assets (referenced from template.js) then it's going to be nasty. |
Closing this as is solved. |
So it would be cool to have all js and css gzipped by default. In case, we may want to have a setting to disable it on the component level? (not sure it is needed).
Gzip support: http://schroepl.net/projekte/mod_gzip/browser.htm
The text was updated successfully, but these errors were encountered: