I'll take a look at this issue this week.  There are a few other
issues in the same vein floating around.

   ---Mark

http://twitter.com/mccv



On Wed, May 26, 2010 at 2:54 AM, noki <noris...@gmail.com> wrote:
> Hi,
>
> I am in trouble with OAuth authentication of Streaming filter method
> with multi tracking words.
>
> I tryed status/filter method with track parameters. When I added one
> key word to track parameter, ex. track=noki, the returned status was
> 200(Authed). On the other hand, I got status 401 on two key words like
> track=noki,twitter or "track=noki twitter"
>
> the url encode may cause this problem but my lib. worked fine on REST
> APIs like status update.
>
> Is this my OAuth library bug or Twitter?
>
> Here is Auth header example.
>
> The tokens used to make sample header is:
> consumer_token = "consumer_token"
> consumer_secret = "consumer_secret"
> access_token = "access_token"
> access_secret = "access_secret"
>
> METHOD: POST
> URL:  http://stream.twitter.com/1/statuses/filter.json
> PARAM: track=noki
>
> makes
>
> oauth_consumer_key="consumer_token",
> oauth_token="access_token",
> oauth_signature_method="HMAC-SHA1",
> oauth_timestamp="1274866253",
> oauth_nonce="69d53e881b216276c58a5368ad8038ea",
> oauth_version="1.0",
> oauth_signature="DEwB5M6sA1%2BKq2Xy%2FYx3nttm%2BGg%3D"
>
> This works fine. but
>
> PARAM: track=noki,twitter
>
> makes
>
> oauth_consumer_key="consumer_token",
> oauth_token="access_token",
> oauth_signature_method="HMAC-SHA1",
> oauth_timestamp="1274866475",
> oauth_nonce="a448e7901d17808677bc46f6a2a180e7",
> oauth_version="1.0",
> oauth_signature="tRnND6u0mbQ%2BVLzAeGxQHvM%2FP3M%3D
>
> but does not work.
>
> Thank you.
> --
> Norio Suzuki
>

Reply via email to