There was a problem today with the authentication database used by one Hosebird servers. This caused an unlucky proportion of connections that require an elevated Role to be rejected. This has been fixed.
Note that Hosebird limits logins by user, not by resource. If you are consuming /gardenhose and /follow from the same account, the first connection may be thrown off by the second connection. -John Kalucki Services, Twitter, Inc. On Jun 4, 2:26 pm, Chad Etzel <jazzyc...@gmail.com> wrote: > I am playing with the follow methods, and they have been acting funny > all day. Lately it just closes immediately. Right now I am just > testing with curl: > > $ curl -v -d @follow.dathttp://stream.twitter.com/follow.json-uuser:pass > > * About to connect() to stream.twitter.com port 80 > * Trying 128.121.146.231... connected > * Connected to stream.twitter.com (128.121.146.231) port 80 > * Server auth using Basic with user 'jcnetstreamr1'> POST /follow.json > HTTP/1.1 > > Authorization: Basic amNuZXRzdHJlYW1yMTpyY2s0OG1udA== > > User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 > > OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5 > > Host: stream.twitter.com > > Accept: */* > > Content-Length: 49 > > Content-Type: application/x-www-form-urlencoded > > > follow=6633812 17281594 19667049 3841961 17243913HTTP/1.1 200 OK > > < Content-Type: application/json > < Content-Length: 0 > < Server: Jetty(6.1.14) > * Connection #0 to host stream.twitter.com left intact > * Closing connection #0 > $ > > I've tried this out on 2 servers, one on the east coast, and one on > the west coast. > > Content-Length is 0, so I guess curl just closes immediately. > > Other times it takes about 30 seconds to get the Response headers back: > > HTTP/1.1 200 OK > < Content-Type: application/json > < Transfer-Encoding: chunked > < Server: Jetty(6.1.14) > > The PHP script I've written to connect to the follow methods is acting > even weirder. I'm using the same basic code as I have to use the > /spritzer stream, which seems to work ok. > > Anyone else with similar behavior on the /follow streams? > > -Chad
