Re: [twitter-dev] Re: /statuses/filter.json returns 401 with OAuth
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 you, - Josiah -- 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
Re: [twitter-dev] Re: /statuses/filter.json returns 401 with OAuth
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 the point of being able to successfully make a call to verify_credentials. I then found that I could stream using a single word, or sequences of words without spaces. It's then I discovered, as you suggested, that the body of the post must be using the OAuth escape method for parameters as per RFC 3986, as opposed to RFC 2396, which I had been using for the body (and which was provided by my language libraries). So frustrating, but I got it working. Thank you for the help. - Josiah -- 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
Re: [twitter-dev] Re: /statuses/filter.json returns 401 with OAuth
Hey Josiah, Glad you got it working. I have an OAuth library I put together which you might want to look at. It's in PHP and shows the OAuth signing process. It also supports multipart uploads and the Streaming API. You can find it on github: https://github.com/themattharris/tmhOAuth Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Feb 23, 2011 at 12:15 PM, Josiah Carlson josiah.carl...@gmail.comwrote: 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 the point of being able to successfully make a call to verify_credentials. I then found that I could stream using a single word, or sequences of words without spaces. It's then I discovered, as you suggested, that the body of the post must be using the OAuth escape method for parameters as per RFC 3986, as opposed to RFC 2396, which I had been using for the body (and which was provided by my language libraries). So frustrating, but I got it working. Thank you for the help. - Josiah -- 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
[twitter-dev] Re: /statuses/filter.json returns 401 with OAuth
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: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: /statuses/filter.json returns 401 with OAuth
Hi Josiah, OAuth is working fine in my tests of the Streaming API. If you are getting errors double check you are encoding the commas correctly in your basestring. For example, if your track terms were: track=twitter,twitter api,twitterapi The basestring should include: track%3Dtwitter%252Ctwitter%2520api%252Ctwitterapi Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Tue, Feb 22, 2011 at 6:38 PM, Josiah Carlson josiah.carl...@gmail.comwrote: 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: 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
