I now changed the request from HTTP 1.1 to HTTP 1.0 as suggested in this post:
http://stackoverflow.com/questions/4581330/twitter-streaming-api-oauth-chunked-response/4581538#4581538 Could this have any negative side-effects? On Jan 4, 3:42 am, "@epc" <epcoste...@gmail.com> wrote: > The streaming API transmits in chunked encoding, it sounds like you > are consuming it raw. > Seehttp://groups.google.com/group/twitter-development-talk/msg/ee8b7024d... > andhttp://groups.google.com/group/twitter-development-talk/msg/69131a43f... > for previous discussions about this. > -- > -ed costello -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
