[twitter-dev] Re: Unauthorized 401 http://twitter.com/friends/ids.json

2010-12-18 Thread Kathy
This is what I get in the response

{request:\/friends\/ids.json?user_id=121552558,error:Incorrect
signature}

Kathy

On Dec 17, 1:28 pm, Matt Harris thematthar...@twitter.com wrote:
 Hi Kathy,

 What is the error we are returning in the response body? It should contain
 information about why the request failed.

 Best
 @themattharris
 Developer Advocate, Twitterhttp://twitter.com/themattharris

 On Fri, Dec 17, 2010 at 11:14 AM, Kathy kathylee1...@gmail.com wrote:
  I still get the same error 401 with url
 https://api.twitter.com/1/friends/ids.json

  Kathy

  On Dec 17, 9:10 am, Tom van der Woerdt i...@tvdw.eu wrote:
   Your url is wrong. Instead, use :
 https://api.twitter.com/1/friends/ids.json

   Tom

   On 12/17/10 2:06 AM, Kathy wrote:

I keep getting unauthorized 401 error.

I have been running my twitter application for months. But past couple
of days, I was able to retieve very few friends information.  Since
Dec. 15,  6pm, I haven't been able to retrieve any.

My search url is :
   http://twitter.com/friends/ids.json?user_id=

  --
  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: Unauthorized 401 http://twitter.com/friends/ids.json

2010-12-17 Thread Kathy
I still get the same error 401 with url   
https://api.twitter.com/1/friends/ids.json

Kathy

On Dec 17, 9:10 am, Tom van der Woerdt i...@tvdw.eu wrote:
 Your url is wrong. Instead, use :https://api.twitter.com/1/friends/ids.json

 Tom

 On 12/17/10 2:06 AM, Kathy wrote:

  I keep getting unauthorized 401 error.

  I have been running my twitter application for months. But past couple
  of days, I was able to retieve very few friends information.  Since
  Dec. 15,  6pm, I haven't been able to retrieve any.

  My search url is :
 http://twitter.com/friends/ids.json?user_id=

-- 
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] Unauthorized 401 http://twitter.com/friends/ids.json

2010-12-16 Thread Kathy
I keep getting unauthorized 401 error.

I have been running my twitter application for months. But past couple
of days, I was able to retieve very few friends information.  Since
Dec. 15,  6pm, I haven't been able to retrieve any.

My search url is :
http://twitter.com/friends/ids.json?user_id=


-- 
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] Is OAuth working for *anyone* out there?

2010-05-20 Thread Kathy ann Scott
i support dossy too 






From: Taylor Singletary taylorsinglet...@twitter.com
To: twitter-development-talk@googlegroups.com
Sent: Thu, May 20, 2010 1:27:26 PM
Subject: Re: [twitter-dev] Is OAuth working for *anyone* out there?

Sorry you're having trouble, Dossy.

Can you share the complete path you're using to fetch a request token (with 
host, domain, protocol, path, and any query parameters), your signature base 
string, and an authorization header if you're using header-based auth?

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod



On Thu, May 20, 2010 at 12:29 PM, Dossy Shiobara do...@panoptic.com wrote:


On 5/20/10 3:16 PM, Taylor Singletary wrote:
 While we have been having some performance issues that should give you
 occasional 401s, it shouldn't be as widespread as the experience you've
 been having.

OK, you know, until *literally* 60 seconds ago, requests for
http://twitter.com/oauth_clients/details/1574 were returning 502 fail
whales.  NOW, it just loaded.

OK, who fixed it just now?  What was broken?


 When we throw a 401, we typically provide an error message within the
 body of the response -- if you can share that it would be helpful.

As I said in my email the other day:

HTTP 401, Failed to validate oauth signature and token


 Has anything about your environment changed?

Sadly, no.  I wish it were that simple.


 Have you reset your consumer key or secret?

No, and I just verified again that it still matches what is showing in
the Twitter OAuth apps page.


 Does this happen for all access tokens or is
 there a specific access token that you use that is failing? Is it
 possible that access token's access was revoked? The error message
 provided on 401s will help shine some light on some of this.

It's happening on the very first, and every single, /oauth/request_token
API call.


 One recent change we made is that if you're trying to access resources
 that don't require authentication, but you are still providing OAuth
 credentials and those credentials are invalid, we no longer provide the
 data but instead properly inform you that your credentials aren't valid.

Again, I'm not even getting as far as making a Twitter API call any
more.  The whole OAuth process is failing at the request_token endpoint.


 Which, if any, OAuth library do you use?

Homegrown.  Has been working for over a year, and has not been modified
the entire time.

--

Dossy Shiobara  | do...@panoptic.com| http://dossy.org/
Panoptic Computer Network   | http://panoptic.com/
  He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on. (p. 70)




  

Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

2010-05-20 Thread Kathy ann Scott
my code 401 . 






From: Cameron Kaiser spec...@floodgap.com
To: twitter-development-talk@googlegroups.com
Sent: Thu, May 20, 2010 1:28:44 PM
Subject: Re: [twitter-dev] Re: Incorrect signature when calling update url   
/1/statuses/update.xml

 FYI - I am writing a .Net based library and so I currently use
 System.Uri.EscapeDataStringhttp://msdn.microsoft.com/en-us/library/system.uri.escapedatastring.aspxto
 do my escaping

I don't know what that routine is, but if it's not RFC 3986 compliant, it
won't work. You might want to roll your own, it's a couple lines of code
and a regex.

-- 
 personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- EH! STEVE! ---