Return to Answer

added 77 characters in body; edited body

edited Jul 24, 2010 at 18:00

18.6k
6
36
62

This should be fixed now.

StackAuth will send down gzip'd content (whether you ask for it or not) just like the API. Content-Encoding is also set, as a debugging aid (for browsers and the like), but bear in mind that proxies love to strip that out so don't rely on its presencepresence*.

_{*Read: keep doing what you were doing in the first place. :)}

This should be fixed now.

StackAuth will send down gzip'd content (whether you ask for it or not) just like the API. Content-Encoding is also set, as a debugging aid (for browsers and the like), but bear in mind that proxies love to strip that out so don't rely on its presence.

This should be fixed now.

StackAuth will send down gzip'd content (whether you ask for it or not) just like the API. Content-Encoding is also set, as a debugging aid (for browsers and the like), but bear in mind that proxies love to strip that out so don't rely on its presence*.

_{*Read: keep doing what you were doing in the first place. :)}

answered Jul 24, 2010 at 17:55

18.6k
6
36
62

This should be fixed now.

StackAuth will send down gzip'd content (whether you ask for it or not) just like the API. Content-Encoding is also set, as a debugging aid (for browsers and the like), but bear in mind that proxies love to strip that out so don't rely on its presence.