Connection limit shared between user and site streams?


#1

When I try to connect to the User Streams endpoint (userstream.twitter.com/1.1/user.json) I get back a 420 “Exceeded connection limit for user” (the verbose curl output is appended below). To my knowledge, there aren’t any other user streams using this OAuth keys/tokens.

I do, however, use the same OAuth information for our site stream connections (sitestream.twitter.com//1.1/site.json). Are the connection limits for this account shared amongst the various streaming endpoints?

-ch

==========

$ curl --get ‘https://userstream.twitter.com/1.1/user.json’ --header ‘Authorization: OAuth oauth_consumer_key=“REDACTED”, oauth_nonce=“REDACTED”, oauth_signature=“REDACTED”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1389044780”, oauth_token=“36183-REDACTED”, oauth_version=“1.0”’ --verbose

  • About to connect() to userstream.twitter.com port 443 (#0)
  • Trying 199.59.148.139…
  • Adding handle: conn: 0x7fa65b007800
  • Adding handle: send: 0
  • Adding handle: recv: 0
  • Curl_addHandleToPipeline: length: 1
    • Conn 0 (0x7fa65b007800) send_pipe: 1, recv_pipe: 0
  • Connected to userstream.twitter.com (199.59.148.139) port 443 (#0)
  • successfully set certificate verify locations:
  • CAfile: /opt/local/share/curl/curl-ca-bundle.crt
    CApath: none
  • SSLv3, TLS handshake, Client hello (1):
  • SSLv3, TLS handshake, Server hello (2):
  • SSLv3, TLS handshake, CERT (11):
  • SSLv3, TLS handshake, Server finished (14):
  • SSLv3, TLS handshake, Client key exchange (16):
  • SSLv3, TLS change cipher, Client hello (1):
  • SSLv3, TLS handshake, Finished (20):
  • SSLv3, TLS change cipher, Client hello (1):
  • SSLv3, TLS handshake, Finished (20):
  • SSL connection using RC4-SHA
  • Server certificate:
  • subject: C=US; ST=California; L=San Francisco; O=Twitter, Inc.; OU=Twitter Security; CN=userstream.twitter.com
  • start date: 2013-10-29 00:00:00 GMT
  • expire date: 2015-10-30 23:59:59 GMT
  • subjectAltName: userstream.twitter.com matched
  • issuer: C=US; O=VeriSign, Inc.; OU=VeriSign Trust Network; OU=Terms of use at https://www.verisign.com/rpa ©10; CN=VeriSign Class 3 Secure Server CA - G3
  • SSL certificate verify ok.

GET /1.1/user.json HTTP/1.1
User-Agent: curl/7.33.0
Host: userstream.twitter.com
Accept: /
Authorization: OAuth oauth_consumer_key=“REDACTED”, oauth_nonce=“REDACTED”, oauth_signature=“REDACTED”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1389044780”, oauth_token=“36183-REDACTED”, oauth_version=“1.0”

< HTTP/1.1 420 Unknown
< Connection: close
< Date: Mon, 06 Jan 2014 21:47:04 GMT
< Content-Length: 36
<
Exceeded connection limit for user

  • Closing connection 0
  • SSLv3, TLS alert, Client hello (1):