Hi Mark,

While we work hard to make our OAuth implementation the same across
resources, the implementation in our streaming API is in a different
language and may still have some quirks in relation to our other end points.

The best way we can help you is for you to show us the HTTP headers you are
sending, the POST body you are sending, and the signature basestring that
goes with it.

Here's an example of using stream.twitter.com with two trivial track terms:
== full_request_url (OAuth Trace)
http://stream.twitter.com/1/statuses/filter.json
==

== signature_base_string (OAuth Trace)
POST&http%3A%2F%2Fstream.twitter.com
%2F1%2Fstatuses%2Ffilter.json&oauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DcR4ElDpk184FKFdlhYIxUyhAKM0xVmKZOBHUIw4Jbo%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1291415057%26oauth_token%3D819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw%26oauth_version%3D1.0%26track%3Dtwitter%252Capple
==

== authorization_header (OAuth Trace)
OAuth oauth_nonce="cR4ElDpk184FKFdlhYIxUyhAKM0xVmKZOBHUIw4Jbo",
oauth_signature_method="HMAC-SHA1", oauth_timestamp="1291415057",
oauth_consumer_key="ri8JxYK2ddwSV5xIUfNNvQ",
oauth_token="819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw",
oauth_signature="Py8QWncBXlZNWgR5sh5pOlaL%2FSA%3D", oauth_version="1.0"
==

== POST body (OAuth Trace)
track=twitter%2capple
==

opening connection to stream.twitter.com...
opened

== request_headers (OAuth Trace)
accept: */*
connection: close
user-agent: OAuth gem v0.3.6
content-type: application/x-www-form-urlencoded
authorization: OAuth
oauth_nonce="cR4ElDpk184FKFdlhYIxUyhAKM0xVmKZOBHUIw4Jbo",
oauth_signature_method="HMAC-SHA1", oauth_timestamp="1291415057",
oauth_consumer_key="ri8JxYK2ddwSV5xIUfNNvQ",
oauth_token="819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw",
oauth_signature="Py8QWncBXlZNWgR5sh5pOlaL%2FSA%3D", oauth_version="1.0"
==

Taylor

On Fri, Dec 3, 2010 at 1:43 PM, Mark Soper <maso...@gmail.com> wrote:

> After using streaming API (statuses/filter) for several months with
> basic auth, I'm trying to make the switch to OAuth, which I'm already
> using successfully against the Site Stream Beta via Tweepy (python).
> Using all the same process that works with Site Stream (except for few
> minor changes to request - e.g. POST instead of GET), I continue to
> get 401 errors with OAuth & statuses/filter.  Could be a signature
> problem on my end, but I've tried a bunch of different configurations
> and nothing has worked.
>
> Anyone have ideas why this might happen?
>
> Thanks,
>
> Mark
> @marksoper
>
> ------------------ about me:
> I'm working on a service called Rally that helps people make plans
> using Twitter. It improves upon the subset of Twitter content that
> refers to future dates (announcements, plans, deadlines, etc.) by
> putting this stuff on a shared schedule so you can be aware of what's
> upcoming without having to have seen it when originally posted.
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to