First, does it worth with curl? Second, you may have a client that doesn't preemptively basic auth, yet fails to respond to the challenge. Try forcing immediate basic auth. You can trace with tcpdump.
Third, stop all Streaming API clients for 15 minutes. Try once with your client, or, ideally, curl -vvv. Examine any text that is returned. If that fails, email me results from all three steps, the time UTC time, account name, URL, any parameters and the intended access level. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Sep 9, 6:15 am, Andrew McCloud <and...@amccloud.com> wrote: > Great news! Unfortunately, i'm still getting a 401 with any account I > try. > > On Sep 8, 8:33 pm, John Kalucki <jkalu...@gmail.com> wrote: > > > A few corner cases were causing excessive rate limiting on the > > Streaming API. One bad login, perhaps due to an unparsable predicate, > > or other minor validation issue, would lock out some users in some > > cases. Another class of users were only allowed in once and were > > subsequently limited. The vast majority of users were unaffected by > > this recently introduced defect. > > > All such cases should be resolved. > > > -John Kaluckihttp://twitter.com/jkalucki > > Services, Twitter Inc.
