[twitter-dev] error 401 from oauth, starting a few days ago

2011-06-15 Thread arlomedia
Last July I installed oauth-php to display items from my user timeline on my website home page. I then copied the setup to another website with another Twitter account and both have been working fine. Then a few days ago both websites started returning error code 401, "This method requires authent

[twitter-dev] Re: error 401 from oauth, starting a few days ago

2011-06-16 Thread arlomedia
Thanks for the reply. On one website, I'm accessing the timeline for a protected account; on the other website, the account is not protected. For both, I'm using this URL: https://api.twitter.com/statuses/user_timeline.xml. Both stopped working last week. The oauth example script I posted above r

[twitter-dev] Re: error 401 from oauth, starting a few days ago

2011-06-16 Thread arlomedia
Hello, I wondered about the version number in the URL; but when I add that, I get the same error. I also removed the token secret from the request parameters. Where would I set the permissions on the API key? I'm not familiar with that process. In any case, my own scripts were just passing the ke

[twitter-dev] Re: error 401 from oauth, starting a few days ago

2011-06-17 Thread arlomedia
Just giving this a bump for Taylor. For anyone else, does the oauth-php example script work with your accounts? It works for me when accessing the public timeline as shown in the example, but if I change the request URL to access my user timeline (protected or unprotected) I get the authorization

[twitter-dev] Re: error 401 from oauth, starting a few days ago

2011-06-24 Thread arlomedia
The response body only includes the text of the error message ("This method requires authentication") and a copy of my request URI. I included my complete request including all headers in an earlier post in this thread; is that what you meant by "authorization header/ parameters"? -- Twitter dev

[twitter-dev] Re: error 401 from oauth, starting a few days ago

2011-06-27 Thread arlomedia
Yes, I've made both of those changes, as I mentioned in my June 16 post. I just ran the requests again; here's what the request headers look like now. The first is the token request and the second is the timeline request: POST https://api.twitter.com/oauth/request_token Authorization: OAuth realm=

[twitter-dev] Re: error 401 from oauth, starting a few days ago

2011-07-01 Thread arlomedia
FYI, one of my clients decided to pull this from the site rather than spend any more money troubleshooting it. I've hidden it from the other site but may come back later and try a different OAuth library if I have time. I can't use the pre-built widgets because they don't offer enough flexibility i