Hello,
We've been using some of the streaming API (specifically
/statuses/filter.json and occasionally /statuses/sample.json), and recently
I have noticed that we are seeing only 420 errors from our auth tokens for
all of our dev, staging, and prod applications. Two sets of those auth
tokens
A small update...
After letting it rest over night, I was able to get /statuses/filter.json to
work on my office machine using any set of keys, but attempting to run with
any keys on ec2 gets us a 420. Immediately after the 420 in ec2, I can run
without issue in the office. I've tried a few of
Okay, fresh, new interesting error code.
Content:
POST /1/statuses/filter.json HTTP/1.1
Host: stream.twitter.com
Accept-Encoding: identity
Content-Length: 30
Authorization: OAuth
realm=http://stream.twitter.com/1/statuses/filter.json;,
oauth_consumer_key=...,
To follow up:
I switched to a GET request, despite the docs saying Use a POST request
header parameter to avoid long URLs.. This seems to have resolved the
issue. Why change now?
- Josiah
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter:
, 2011 at 1:08 PM, Josiah Carlson josiah@gmail.comwrote:
Now that I've got OAuth with statuses/follow.json working, I've been
working through building a small part of our app.
Part of the streaming API docs state that only one connection is allowed
(reasonable). Upon making a second
Now that I've got OAuth with statuses/follow.json working, I've been working
through building a small part of our app.
Part of the streaming API docs state that only one connection is allowed
(reasonable). Upon making a second connection, the first no longer receives
any data (not even
themattharris,
Thank you for the response.
I can only (easily) test quoting of the body after signing, and that results
in OAuth authorization failure.
Which client library do you use? I'd like to trace though a known-working
library to figure out where the one I am using is failing.
Thank
Looking at 3rd party libraries, I realized how ... nasty their auth flows
were, so I walked through the pieces of:
http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/
and
created my own simple OAuth function with the proper encodings, escapes,
etc. That got me to
Does no one else use /statuses/filter.json? Has no one gotten it to work
with OAuth?
- Josiah
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
Long story short: I can access the REST API using OAuth without issue. I can
access the streaming API using Basic Auth without issue. When I try to
access the streaming API using OAuth, I get a 401 error.
I filed a bug http://goo.gl/nXYg2, but was directed here and to the IRC
channel. I posted
10 matches
Mail list logo
