yusuke/twitter4j — pull request #8 by xhanin (2012-04-05 23:57:31+00:00)
Title: Bug with content-encoding: gzip on GAE with current twitter service

Hi,

I've just spent some time investigating why twitter4j was not working properly on GAE in my use case, and it seems the problem is not just me. After a cumbersome investigation, I've found that twitter is now returning the content-encoding header in lower case, which breaks the test on Content-Encoding = gzip in the http response impl on GAE. Thus the content is read with a plain inputstream instead of through gzip, leading to bad content and strange errors (in my case it was the post to obtain a oauth request token which was leading to bad content, badly parsed in OAuthToken class, and therefore a null token.

The fix is pretty simple, I hope you will be able to integrate it if you confirm the problem.

Cheers, and thanks for the hard work!