I read previous discussions on 401s, ensure the clock is synced. Really hope you can help with my case.
Sometimes, the streaming API client I wrote would get back 401, trying to connect to Sample or Filter stream. This the example for last failing request (user: @trscs1)
Base string: POST&https%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses%2Ffilter.json&oauth_consumer_key%3DP1i7xB4I2bjlB7Y3E3iOg%26oauth_nonce%3DcYaYcOZNsEe%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1327452066%26oauth_token%3D473447730-A9gisdNgScrSBxqqH7u5x7v4TknpLqUdDNgM5P7s%26oauth_version%3D1.0%26track%3DThailand
Signature string: I9tLP0Ab0+Wzf2k3Lso1VCFdycE=
This is info in the request HTTP headers:
Authorization: OAuth realm="",oauth_signature="I9tLP0Ab0%2BWzf2k3Lso1VCFdycE%3D",oauth_nonce="cYaYcOZNsEe",oauth_signature_method="HMAC-SHA1",oauth_timestamp="1327452066",oauth_consumer_key="P1i7xB4I2bjlB7Y3E3iOg",oauth_token="473447730-A9gisdNgScrSBxqqH7u5x7v4TknpLqUdDNgM5P7s",oauth_version="1.0"
Twitter responded with:
HTTP ERROR: 401
Problem accessing '/1/statuses/filter.json'. Reason:
// multiple white space chars here
Here are the response HTTP headers:
WWW-Authenticate: Basic realm="Firehose"
The 401 is fairly easy to reproduce. In 10 consecutive attempts in a debugging session, I would get 401 multiple times. I understand that Twitter would tolerate a few repeated connection/disconnection. Can I get banned or 401 for this?