Why do we get 'transfer closed with outstanding read data remaining' from twitter search api


#1

Hi,

since the beginning of day we’ve been having this problem and it’s getting more frequant, at the point where it always fail giving the following :
request :

GET /1.1/search/tweets.json?include_entities=1&count=100&include_rts=1&q=%23plq+OR+%23qs+OR+%23pq+OR+%23caq+OR+%23adq+OR+%23opnat&lang=fr HTTP/1.1
Host: api.twitter.com
User-Agent: Mozilla/4.0 (compatible;)
Accept: /
Accept-Encoding: identity
X-Forwarded-For: 172.16.101.130
Connection: close
Authorization: OAuth oauth_nonce=“knHI7”, oauth_timestamp=“1374614042”, oauth_consumer_key=“SJMWqWkA9iZfSwGqAs9w”, oauth_signature_method=“HMAC-SHA1”, oauth_version=“1.0”, oauth_
token=“5434692-jfimTaQsxSQ0tGrDABhTvwi9IKrhAR8Rx2ed4LDb60”, oauth_signature=“O6QJ6oBpyR%2ByOxPQ28374M5L%2BUM%3D”

Response:

< HTTP/1.1 200 OK
< cache-control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
< content-length: 391082
< content-type: application/json;charset=utf-8
< date: Tue, 23 Jul 2013 21:14:02 GMT
< expires: Tue, 31 Mar 1981 05:00:00 GMT
< last-modified: Tue, 23 Jul 2013 21:14:02 GMT
< pragma: no-cache
< server: tfe
< set-cookie: guest_id=v1%3A137461404262088778; Domain=.twitter.com; Path=/; Expires=Thu, 23-Jul-2015 21:14:02 UTC
< status: 200 OK
< strict-transport-security: max-age=631138519
< x-access-level: read-write
< x-frame-options: SAMEORIGIN
< x-rate-limit-limit: 180
< x-rate-limit-remaining: 178
< x-rate-limit-reset: 1374614582
< x-transaction: 6eac2269af2481df
< x-xss-protection: 1; mode=block
< Transfer-Encoding: chunked
< Connection: close
<

  • Closing connection #0

curl returns us a error #18 : transfer closed with outstanding read data remaining

I tried to find out what’s going on and stumbled on this : https://dev.twitter.com/discussions/15989

Also, I already had some similar issue in the past that was linked to a node on your side having a bug(if it can help)

How can i fix my problem ?

Thank you !


#2

We’re looking into this issue right now. Thanks for reporting it!


#3

We’ve identified the issue and are working to resolve it. Thanks again.


#4

Hi, any progress with this issue?


#5

I believe this should be resolved. Are you still seeing issues with chunked transfer encoding?