The HTTPS protocol, as used in unspecified web applications, can encrypt compressed data without properly obfuscating the length of the unencrypted data, which makes it easier for man-in-the-middle attackers to obtain plaintext secret values by observing length differences during a series of guesses in which a string in an HTTP request URL potentially matches an unknown string in an HTTP response body, aka a "BREACH" attack, a different issue than CVE-2012-4929.
https://www.djangoproject.com/weblog/2013/aug/06/breach-and-django/
https://www.blackhat.com/us-13/briefings.html#Prado
https://support.f5.com/csp/article/K14634
https://bugzilla.redhat.com/show_bug.cgi?id=995168
http://www.kb.cert.org/vuls/id/987798
http://www.iacr.org/cryptodb/archive/2002/FSE/3091/3091.pdf
http://slashdot.org/story/13/08/05/233216