Being safe looking for content-encoding header
I managed to bump into a situation with stream.twitter.com where the content encoding header was not in the headers ... so I am making the check more robust to handle the case where the header is not there.
@sixohsix can you consider merging this in before the micro version bump.