I requested gzip as well for a static media site (https) and they said: Our front-end Nginx server will not use gzip compression for requests > served over HTTPS. This is by design as a mitigation for the BREACH > exploit <https://en.wikipedia.org/wiki/BREACH>. > > We've an internal feature ticket open to consider making the mitigation > optional for customers that don't need it. I will make a note of your > inquiry there. >
Perhaps you can +1 them on this feature request. However, if you're serving your static files via web2py itself (and not via a static app on another domain for speed) then web2py will send the .gz file version of a requested asset if it exists. For example, a request for mysite.css comes in, web2py sends mysite.css.gz automatically if it exists, else it sends mysite.css. The zip_static_files.py utility in your web2py scripts directory will create gzipped versions of all your static files for you. HTH, -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/fbf7bf49-869a-4de0-84a4-6891be8e2fafo%40googlegroups.com.
