Dumb question: Is this general advice or is it specific to django due to the "BREACH" [1][2] https attack? It's not clear if it the underlying flaw is in using a CSRF token or something specific to django's implementation. I had never heard this before, so thank you.
[1] http://news.softpedia.com/news/Django-BREACH-Attack-Against-... [2] http://stacks.11craft.com/what-is-breach-how-can-we-protect-...
You can still use, say, HTML minification.
You can compress your js and css as long as you make sure you aren't sending your confidential information in those request/response headers. A good way to do this is to setup a subdomain for media that never uses cookies.
That said, it seems on nginx TLS compression was not enabled by default, so we are ok (for this known vulnerability).
Basically you need a cookie-less HTTPS subdomain for your static media, and a www.example.com HTTPS domain for your content.