# UPDATE 1 : This was due to BREACH, a hack which attacks compressed https traffic.
# UPDATE 2 : GZIP compression over https is BACK! (as of January 2014) … the mystery continues …
Unfortunately, there seems to be something mysterious going on with compression within SharePoint online.
Back in the day, SharePoint would accept this header correctly, and return a zipped response. Pretty handy when you are returning oodles of JSON. (Would be even handier if it also allowed you to submit a zipped POST – as compression would be even more awesome over oodles of XML … but, maybe a rant for another day).
This is what it used to look like: although the response is 2.8mbs, the server is only returning 120kb.
Unfortunately, for some reason SharePoint online is no longer compressing its responses correctly.
So, now it looks more like this: a 40mb response to an executeQueryAsync is transferring the full 40mb. (What on earth do you have to do to get a 40mb response to ProcessQuery? Long story.)
That’s pretty … frustrating.
Anyway – hopeful we see a fix / workaround soon. Seems pretty wasteful.