Content-Encoding not always being set for gzip'ed reponses


We are randomly seeing the Content-Encoding header being omitted for some gzip’ed responses (only seen it on statuses/user_timeline.json but might affect other endpoints). This causes our Java client to not inflate the response and when it attempts to parse the response.

As a workaround we are assuming that the response is going to be gzip’ed if we requested it but we’d rather not have to make this assumption as it would fail if a non-gzip’ed response was sent.


Thanks for this report. I’ll send it along to the team.