[twitter-dev] Re: 401 Unauthorized in Python/Twisted app

Hi Eryn, I'm not too familiar with the Twisted framework or its implementation of OAuth, so take what I recommend with a grain of salt. * Access tokens generated through the OAuth flow on Twitter, regardless of the technique used (PIN code, xAuth, vanilla OAuth) are long-lived and do not expire u

[twitter-dev] Re: 401 unauthorized on blackberry after appending ";interface=wifi"

The problem could be the length of status or encoding of status is invalid or status in not be included in the sign base string. I have a workable integration now. Check the code here https://github.com/Yincan/blackberry_twitter_oauth On Apr 14, 5:58 am, Mickey wrote: > Still receiving401during

Re: [twitter-dev] Re: 401 Unauthorized Responses to requests signed with whitelisted account

Hi Chris, Our policy team are the beat ones to contact about this as they have access to the information about why the app was suspended. You can contact them through a...@twitter.com . When you contact them let then know what you've put in the email below and include the ticket number of your

[twitter-dev] Re: 401 Unauthorized Responses to requests signed with whitelisted account

Hi Matt, Thank you so much for your timely response. Your suggestion was very helpful - I logged the response body and am seeing the following error: "Invalid / suspended application" I really don't know why that would be - does that mean that we are blacklisted? I should point out a few things

[twitter-dev] Re: 401 Unauthorized Responses to requests signed with whitelisted account

Hi Matt, Thank you so much for your timely response. Your suggestion was very helpful - I logged the response body and am seeing the following error: "Invalid / suspended application" I really don't know why that would be - does that mean that we are blacklisted? I should point out a few things

[twitter-dev] Re: 401 unauthorized on blackberry after appending ";interface=wifi"

Still receiving 401 during update status. There are 2 parts of my code that uses the HttpConnection where I was adding connection transport string. 1. To get the OAuth access token. The end point is "https:// api.twitter.com/oauth/request_token". I removed the code to add transport string here. So

[twitter-dev] Re: 401 unauthorized on blackberry after appending ";interface=wifi"

There are two possible issue you are having.. Most likely you simply need to append the network transport AFTER all signatures have been generated. If you append it before, then those additional characters are being included in the signature but the BlackBerry does not actually send that part of t

[twitter-dev] Re: 401 unauthorized

The https to http hack worked for me consistently for a while but now even this no longer works for my app. Can anyone else confirm this? On Mar 30, 8:10 am, Nick Spacek wrote: > > Sorry, what hack is that?  I've heard a bunch of advice on working > > around this, but nothing conclusive. > > I b

[twitter-dev] Re: 401 unauthorized

> Sorry, what hack is that?  I've heard a bunch of advice on working > around this, but nothing conclusive. I believe he means changing from https://api.twitter.com to http://api.twitter.com. I can confirm that this works for me as well. Obviously not ideal, but an interim solution? -- Twitter d

Re: [twitter-dev] Re: 401 unauthorized

On Mon, Mar 28, 2011 at 10:40 AM, Trevor Dean wrote: > I know Twitter is still working on finding a fix but it's been a couple of > weeks now and it might be a good idea to implement the https to http hack > for now until they resolve the issue.  I was hoping there would be a fix by > now but I ca

Re: [twitter-dev] Re: 401 unauthorized

I know Twitter is still working on finding a fix but it's been a couple of weeks now and it might be a good idea to implement the https to http hack for now until they resolve the issue. I was hoping there would be a fix by now but I can't wait any longer so I will be making that change. On Mon,

[twitter-dev] Re: 401 unauthorized

Are you guys still experimenting the issue? My application is still very unstable, got the Unauthorized all the time. Anyone knows if we have to change our application, or Twitter will fix the problem? Thanks. On 24 mar, 10:44, Ninjamonk wrote: > Thanks for the link to the issue, now I can watch

[twitter-dev] Re: 401 unauthorized

I am using Twitterizer (.NET) and I am also experiencing this issue. This is very annoying... On Mar 23, 7:35 pm, Milos Golubovic wrote: > I can also confirm this behavior.  Is it me or is everyone in here > using .NET? Did I possibly miss somewhere that this is a .NET forum? > I am also using a

[twitter-dev] Re: 401 unauthorized

Thanks for the link to the issue, now I can watch it. I have reverted to the http work around which I hate due to the lack of security. On Mar 24, 1:11 pm, Trevor Dean wrote: > Yes I was also hoping or a more recent update, the last one was over 18 > hours ago and didn't provide much detail > (h

Re: [twitter-dev] Re: 401 unauthorized

Yes I was also hoping or a more recent update, the last one was over 18 hours ago and didn't provide much detail ( http://code.google.com/p/twitter-api/issues/detail?id=2118). On Thu, Mar 24, 2011 at 7:56 AM, Ninjamonk wrote: > any news on this? bit of a joke that it's been going on for a week n

[twitter-dev] Re: 401 unauthorized

any news on this? bit of a joke that it's been going on for a week now and we have no eta on a fix. I have 2 apps waiting to release but as they feature sign in with twitter I cannot do it. One is for the new F1 season which kicks off this weekend... On Mar 24, 2:46 am, Craig Walls wrote: > No, I

Re: [twitter-dev] Re: 401 unauthorized

No, I'm using the Java-based Spring Social for this. And I've seen other threads describing the same problem with PHP. Definitely not just a .NET problem. On 3/23/11 6:35 PM, Milos Golubovic wrote: I can also confirm this behavior. Is it me or is everyone in here using .NET? Did I possibly

[twitter-dev] Re: 401 unauthorized

I can also confirm this behavior. Is it me or is everyone in here using .NET? Did I possibly miss somewhere that this is a .NET forum? I am also using a .NET library (Twitterizer). Wondering if anyone not using .NET is experiencing this issue? On Mar 23, 8:21 am, Craig Walls wrote: > I've just

[twitter-dev] Re: 401 unauthorized

Correction. Switching to HTTP does remove the issue, so I'm making that a configurable setting in our app as a temporary workaround. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: ht

[twitter-dev] Re: 401 unauthorized

I'd like to add another confirmation of this issue. I am the lead developer for a commercial application that has started receiving reports of Twitter sign-in failures over the last couple days and I was able to reliably reproduce the 15-second workaround before I came across this thread. I'm u

[twitter-dev] Re: 401 unauthorized

I've just confirmed what Gary M says...switching to HTTP does seem to make it work. But HTTPS requires a >15 second delay between obtaining a request token and exchanging it for an access token. On Mar 23, 1:48 am, Gary M wrote: > Correction. Switching to HTTP does remove the issue, so I'm making

[twitter-dev] Re: 401 unauthorized

I am seeing exact same behavior (only works with delay) and am using Twitterizer Library. I am new to Twitter and Twitterizer libarary and though I was doing something wrong. Clearly not. Thanks for posting this. On Mar 22, 1:42 pm, Craig Walls wrote: > Okay, more information for you to consid

[twitter-dev] Re: 401 unauthorized

Okay, more information for you to consider... - I am using HTTPS in the requests - I am using the api subdomain in the OAuth requests First, the failed attempt: I fetched the request token: oauth_timestamp: 1300825895 Date header in response: [Tue, 22 Mar 2011 20:31:36 GMT] I then author

[twitter-dev] Re: 401 unauthorized

I'm seeing the same thing that Ninjamonk reported on Mar 20 at 10:10am. That is, if I pause before asking for the access token, it will work. The only difference is that Ninjamonk said he paused for 10 seconds...I found that I have to pause for at least 15 seconds. I also discovered that just waiti

[twitter-dev] Re: 401 unauthorized

oewAGOgpAdXNlZHsA--dad7912a647454357cfa6f0d07804b5c4b5 > d6ae4; domain=.twitter.com; path=/; HttpOnly > Server: hi > Vary: Accept-Encoding > Keep-Alive: timeout=15, max=100 > Connection: Keep-Alive > > oauth_token=...&oauth_token_secret=...&user_id=14051560&screen_name=tat

RE: [twitter-dev] Re: 401 unauthorized

me=tathamoddie I’m noting that the time offset here is only about 4 seconds, however it certainly takes longer than that to work. You can see this for yourself trying to sign in to http://ivebeen.to -- Tatham Oddie au mob: +61 414 275 989, us cell: +1 213 280 3556, skype: tathamoddie If you’re prin

Re: [twitter-dev] Re: 401 unauthorized

If you're experiencing this issue, can you please provide these additional details: * are the OAuth URLs you are using http or https? * do your OAuth URLs contain the api subdomain? (you really should be if you aren't) * what OAuth library (if any) are you using to sign your requests? * If

Re: [twitter-dev] Re: 401 unauthorized

Thanks everyone for the detailed information in these reports; they'll help a lot while we track down the issue. Will update this thread when we know more. @episod - Taylor Singletary - Twitter Developer Advocate On Mon, Mar 21, 2011 at 6:03 AM, Tatham Oddie wrote:

[twitter-dev] Re: 401 unauthorized

Please go and star this issue: http://code.google.com/p/twitter-api/issues/detail?id=2118 On Mar 19, 11:47 pm, Trevor Dean wrote: > Is anyone else experiencing any 401 errors all of a sudden?  I was doing > some testing this morning and was logging in fine using twitter and then 10 > min later I

[twitter-dev] Re: 401 unauthorized

I'm getting this same behaviour on http://ivebeen.to If I wait about 30 seconds before trying to convert the request token to an access token, it all works fine. This happens on both my local machine and on the deployed website - two distinct machines in different locations, timezones, etc. Both

Re: [twitter-dev] Re: 401 unauthorized

Yup, totally stopped working for me as well and my scenario is the same as Joe's too. Any status updates on this issue? On Sun, Mar 20, 2011 at 2:09 PM, akiyoshi wrote: > Well it stopped working for me as well. My scenario was the same as > Joe Mayo's till yesterday. > > On 20 mar, 13:21, Ninja

[twitter-dev] Re: 401 unauthorized

Well it stopped working for me as well. My scenario was the same as Joe Mayo's till yesterday. On 20 mar, 13:21, Ninjamonk wrote: > well it's stopped working completely now even if I pause. > > Can someone from twitter let us know the progress of this bug? > > On Mar 20, 3:28 pm, Joe Mayo wrote:

[twitter-dev] Re: 401 unauthorized

Hi Matt, Here's mine: GET https://twitter.com/oauth/request_token HTTP/1.1 Authorization: OAuth oauth_callback="oob",oauth_consumer_key="sanitized",oauth_nonce="sanitized",oauth_signature_method="HMAC- SHA1",oauth_signature="sanitized",oauth_version="1.0",oauth_timestamp="sanitized" User-Agent: D

[twitter-dev] Re: 401 unauthorized

well it's stopped working completely now even if I pause. Can someone from twitter let us know the progress of this bug? On Mar 20, 3:28 pm, Joe Mayo wrote: > I'm seeing the same problem with 401's during authentication.  I have > an app that has worked flawlessly (with no code changes) for mo

[twitter-dev] Re: 401 unauthorized

I'm seeing the same problem with 401's during authentication. I have an app that has worked flawlessly (with no code changes) for months that is now receiving 401's. I'm also have multiple support issues on users experiencing intermittent 401 errors. For some apps, every authentication request r

[twitter-dev] Re: 401 unauthorized

I am still getting this issue and I think it's time related at twitters end. steps: 1. go to twitter and let user auth app 2. on return use verifier and token to ask twitter for the tokens and get a 401 Now if I pause step 2 before asking twitter for the tokens for 10 seconds it works fine. Thi

[twitter-dev] Re: 401 Unauthorized responses on OAUTH

I'm having the same problem, using a variety of php "libraries". But is ALL 401, no one 200. -- 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/issu

[twitter-dev] Re: 401 Unauthorized responses on OAUTH

I am also getting these problems. They have been on and off all day. The same code works fine and 5 mins later it throws 401's and its been working for 6 months no problem. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/tw

[twitter-dev] Re: 401: Unauthorized (Python)

Hey John, So a couple of things i've noticed. 1. You are using https://twitter.com instead of https://api.twitter.com 2. Maybe i'm following your flow incorrectly but it looks like you are passing the OAuth parameters twice. Once in the URL parameters and once in the body? 3. You are passing an o

[twitter-dev] Re: 401: Unauthorized (Python)

Matt, The response is empty, that's what I'm curious about. I've included the uri, headers, body and request variables below. This request was performed at 2/5/2011 12:06. Uri = 'https://twitter.com/oauth/request_token? oauth_nonce=47248509&oauth_timestamp=1296925690&oauth_consumer_key=h3bOaVfTr8

Re: [twitter-dev] Re: 401: Unauthorized (Python)

Hi John, That dict object doesn't contain the response body. In the response body we give an error reason such as 'Invalid signature', or 'timestamp out of bounds'. Best, Matt On Feb 4, 2011, at 17:37, john wrote: > Hi Matt, > > Thanks for responding. I've posted the response below (as a pyt

[twitter-dev] Re: 401: Unauthorized (Python)

Hi Matt, Thanks for responding. I've posted the response below (as a python dict). {'status': '401', 'content-length': '1', 'x-xss-protection': '1; mode=block', 'x-transaction': 'Sat Feb 05 01:33:54 + 2011-76395-3097', 'set-cookie': 'k=74.128.37.77.1296869634703204; path=/; expires=Sat, 12-Fe

[twitter-dev] Re: 401 Unauthorized errors with Progress Open Edge using xAuth to get Access token

Hi Taylor: For your interest (In case someone else asks): We now have oAuth/xAuth working for Progress open edge and have the basic Twitter status and command functions operational as they were before. There is sample source and Progress open edge twitter libraries we are working on now at http://

[twitter-dev] Re: 401 Unauthorized errors with Progress Open Edge using xAuth to get Access token

We now have oAuth/xAuth working for Progress open edge and have the basic Twitter status and command functions operational as they were before. You can find sample source and Progress open edge twitter libraries we are working on now at http://www.coresoft.com.au/coreforum/index.php?PHPSESSID=87aaa

[twitter-dev] Re: 401 Unauthorized. Frustrating!!!

What does the body of the response read? On Aug 21, 2:54 pm, Mukha Mudra wrote: > Hi, >     I am doing a GET request with query parameters as > followshttp://api.twitter.com/oauth/request_token?oauth_callback="oob"&oauth_consumer_key="N3jplhm1n1ypCzg2eWEg2w"&oauth_signature_method="H > MAC-SH

[twitter-dev] Re: 401 Unauthorized. Frustrating!!!

Ok i tried again with Authorization header. It is as follows OAuth oauth_nonce="RF8P1N7n60mE",oauth_callback="oob",oauth_signature_method="HMAC- SHA1",oauth_timestamp="1282404507",oauth_consumer_key="N3jplhm1n1ypCzg2eWEg2w",oauth_signature="S0tx5EeTGk1m %2BcH5HMmjg6UTW9U%3D",oauth_version="1.0" Ca

[twitter-dev] Re: 401 Unauthorized with oauth gem

I found out that my app switched from read-write to read only. I didn't get any email about that. Bummer. -Fabio. On Fri, Apr 23, 2010 at 12:17 AM, Spiceee wrote: > > Did anything change in the API (couldn't find anything in the API > changelog) that would make all new users who are associating

Re: [twitter-dev] Re: 401 Unauthorized

Everything looks fine with your POST conversation. Can you email directly with more details? 1) What library/tool are you using to make your POSTs? 2) What are the OS/architectures you're running on in your different environments? 3) Are there odd characters in the password? (could this be a chara

[twitter-dev] Re: 401 Unauthorized

Hi Mark, Thanks for your reply! Screen name of the account is dmlreach. Please see the request and 2 responses. Request: GET /1/account/verify_credentials.xml HTTP/1.1 Authorization: Basic Host: api.twitter.com OK response headers: Status: 200 OK X-Transaction: 1269267625-43203-17004 X-RateLi

Re: [twitter-dev] Re: 401 Unauthorized

Without more details it's tough to say. Do you at least have the screen name of the account in question, and details on both the success and failure environments? ---Mark http://twitter.com/mccv On Wed, Mar 17, 2010 at 1:39 AM, Uladzimir Pashkevich < v.pashkev...@gmail.com> wrote: > Does an

[twitter-dev] Re: 401 Unauthorized

Does anyone has any ideas? Any help is really appreciated, because I can't understand this kind of the API's behavior. On Mar 12, 6:40 pm, Uladzimir Pashkevich wrote: > Hi everyone, > > I am developing an application using Twitter API and I have > encountered into a strange behavior connected wit

Re: [twitter-dev] Re: 401 - Unauthorized error when diacritics in status

Thanks Mageuzi. I had done some searching be never came across that thread. Guess I wasn't searching for the right words. Thanks. On Tue, Feb 23, 2010 at 2:45 PM, Mageuzi wrote: > I'm not sure if this is the same issue you are encountering, but I had > a similar issue in my C# twitter app. T

[twitter-dev] Re: 401 - Unauthorized error when diacritics in status

I'm not sure if this is the same issue you are encountering, but I had a similar issue in my C# twitter app. The post I made is here: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/ef11efdd0a9cf194/6950ce9721a48609#6950ce9721a48609 On Feb 23, 2:13 pm, Ryan Alford

Re: [twitter-dev] Re: 401 unauthorized

Our external monitoring is accessing API calls with OAuth just fine. Are you still running into this issue? If so, can you provide more details? ---Mark http://twitter.com/mccv On Sat, Jan 2, 2010 at 7:53 AM, Greg wrote: > I'm having the same issue. I've tried to across other sites and it

[twitter-dev] Re: 401 unauthorized

I'm having the same issue. I've tried to across other sites and it still doesn't work. On Dec 31 2009, 4:05 am, Vignesh wrote: > My website uses twitter for authentication, > For the past 24 hours the OAuth sign in is continuously returning > 401 , i am not able to figure out what to do? > Has so

[twitter-dev] Re: 401 Unauthorized problem

I submitted a bug, vote for it: http://code.google.com/p/twitter-api/issues/detail?id=1294&colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component On Dec 3, 11:13 am, Wilfred yau wrote: > I have try that put the _method=DELETEin Header, but still not > wor

[twitter-dev] Re: 401 Unauthorized problem

I have the same problem. I've tried to not include the _method param from signature computing, didn't work any better. On Dec 3, 11:13 am, Wilfred yau wrote: > I have try that put the _method=DELETEin Header, but still not > work... > do anyone know if it is Twitter API bug or it is my problem..

[twitter-dev] Re: 401 Unauthorized problem

I have try that put the _method=DELETE in Header, but still not work... do anyone know if it is Twitter API bug or it is my problem... this problem stop the development of my new Twitter Client in Firefox... Thanks Wilfred On Nov 27, 1:24 pm, Mark McBride wrote: > It looks like you're trying to

[twitter-dev] Re: 401 Unauthorized problem

I'm having the same problem. I can't delete members from lists using oAuth. I've tried using the DELETE method and adding the _method=DELETE parameter. All of the combinations return a "401 Unauthorized" error.

[twitter-dev] Re: 401 Unauthorized problem

I have try to follow to OAuth document to set up Authorization header, but still get 401 Unauthorized when I am using _method as parameter, and here is the result: *Response Headers DateTue, 01 Dec 2009 03:21:03 GMT Serv

Re: [twitter-dev] Re: 401 Unauthorized problem

It looks like you're trying to actually include the OAuth Authorization header in your POST body, which isn't the way you want to do it. Instead, you should be using the Authorization HTTP header to transmit this info (see http://oauth.net/core/1.0a#anchor46). To make things extra weird, in one c

[twitter-dev] Re: 401 Unauthorized problem

I have already solve the special char problem because encoding in Flex. but I still find that when I call _method= DELETE in List API, I still get 401 Unauthorized from api.twitter.com. On Nov 25, 11:09 am, Wilfred yau wrote: > I am using OAuth to accessListAPI, but I find that if the request > U

[twitter-dev] Re: 401 Unauthorized -- user_timeline -- using Numeric ID

Thanks for all of your help! At some point, the 401 error for User Not Found should be changed to a 404. The fix would make this type of fetch much more efficient, and save on the number of API calls. I adapted my code for what you suggested above, but I had to check for User Not Found which req

[twitter-dev] Re: 401 Unauthorized -- user_timeline -- using Numeric ID

If you try to pull a protected users' timeline w/o authentication then it will throw a 401. You can confirm whether a user id is valid by trying to call: http://twitter.com/users/show.xml?id={insert_id_here} users/show will throw a 404 on a non existent user. -Chad On Wed, Oct 21, 2009 at 1:43

[twitter-dev] Re: 401 Unauthorized -- user_timeline -- using Numeric ID

*bangs head on desk...again* Now that I know what what my Twitter ID is, and I know that I am a valid user, I tried it and it worked. It's gone way past 15 users now without a problem (without error checking). I see what is happening now. After 15 users or so, I hit a user that no longer exists.

[twitter-dev] Re: 401 Unauthorized -- user_timeline -- using Numeric ID

I think I see what is happening now. After 15 users or so, I hit a user that no longer exists. On a 404, I skip the user, but on a 401, for the time being, I am retrying, and then maxing out my hourly limit. The other part was my overworked mind. I was pulling numbers that looked like Twitter IDs

[twitter-dev] Re: 401 Unauthorized -- user_timeline -- using Numeric ID

Hi Ryan, I think part of the problem is that user id 1255997062 does not exist, so it should really be returning a 404 instead of a 401. Do you get the same 401 result with a known valid user id? -Chad On Tue, Oct 20, 2009 at 3:13 PM, Ryan Rosario wrote: > > Correct. I thought that was weird,

[twitter-dev] Re: 401 Unauthorized -- user_timeline -- using Numeric ID

Correct. I thought that was weird, but didn't know what to make of it. Same IP. The unauthenticated call was from an IP that is not whitelisted, so 150/hr. The second call was from the same IP, but authenticated as a whitelisted account, so should be 2/hr. I usually only work from the whiteli

[twitter-dev] Re: 401 Unauthorized -- user_timeline -- using Numeric ID

Apart from the 401 issue, the following is also very weird: < X-experimental-RLS-remaining: 0 < X-experimental-RLS-maxvalue: 150 < X-RateLimit-Limit: 2 This is on the second authenticated call. On the unauthenticated call X-RateLimit-Limit was 150. I assume both calls were made from the same

[twitter-dev] Re: 401 Unauthorized -- user_timeline -- using Numeric ID

Below are the responses. I tried various combinations of - uusername:pass -u=username:pass -u username:pass and each time got an authentication error. Without authentication [madhatter:~/Desktop] ryan% curl -vvv http://twitter.com/statuses/user_timeline.json\?user_id=1255997062\&count=100 * About

[twitter-dev] Re: 401 Unauthorized -- user_timeline -- using Numeric ID

Hi Ryan, This sounds like a bug. Can you provide full HTTP request/response headers+body traces for some of these requests? (be sure to obscure the authentication header). Using curl -vvv would be good. -Chad On Tue, Oct 20, 2009 at 1:10 PM, Ryan Rosario wrote: > > I have been running into a r

[twitter-dev] Re: 401 Unauthorized error while posting status with Unicode characters (non english characters)

Thanks, I will try that! On Sat, Sep 26, 2009 at 8:11 AM, JDG wrote: > That's true -- %5BB6, for example, is NOT a UTF-8 encoded codepoint for a > character. It's Unicode (or UTF-16). > > On Fri, Sep 25, 2009 at 20:54, Mageuzi wrote: > >> >> Hello, >> I had this same problem. I had to convert

[twitter-dev] Re: 401 Unauthorized error while posting status with Unicode characters (non english characters)

That's true -- %5BB6, for example, is NOT a UTF-8 encoded codepoint for a character. It's Unicode (or UTF-16). On Fri, Sep 25, 2009 at 20:54, Mageuzi wrote: > > Hello, > I had this same problem. I had to convert all multi-byte characters > into their individual bytes. > So, for example, for the

[twitter-dev] Re: 401 Unauthorized error while posting status with Unicode characters (non english characters)

Hello, I had this same problem. I had to convert all multi-byte characters into their individual bytes. So, for example, for the character "の": Your example has %306E, but the encoding that works for me is %E3%81%AE (three bytes for the three-byte character). On Sep 25, 5:00 pm, Satheesh Natesa

[twitter-dev] Re: 401 Unauthorized error while posting status with Unicode characters (non english characters)

Yes, it is UTF-8 encoded. The request body for "の脚本家が贈る" is oauth_consumer_key=wmeO7Y20oMFa1ptKVY4WA&oauth_nonce=3231757&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1253903495&oauth_token=76084396-0M9ll2nghrjWhjALbH7YEHXizcLDNvoLfgXKfHQZQ&oauth_version=1.0&status=%306E%811A%672C%5BB6%304C%8D0

[twitter-dev] Re: 401 Unauthorized error while posting status with Unicode characters (non english characters)

Are you sure you are encoding your posts as UTF-8? On Sep 24, 5:16 pm, Satheesh Natesan wrote: > I am getting "401 Unauthorized" exception when updating status with > non english characters using my app. > > This exception is happening for any Japanese or Korean characters. > > Another interesti

[twitter-dev] Re: 401 Unauthorized...

Are you getting anything in the response body with the 401? On Wed, Aug 12, 2009 at 2:22 PM, Alex Payne wrote: > To the best of my knowledge, we're not doing any unusual blocking. Rate > limits are as they have been. > > > On Wed, Aug 12, 2009 at 08:08, AccountingSoftwareGuy < > virga.rob...@gma

[twitter-dev] Re: 401 Unauthorized...

To the best of my knowledge, we're not doing any unusual blocking. Rate limits are as they have been. On Wed, Aug 12, 2009 at 08:08, AccountingSoftwareGuy wrote: > > Is Twitter still blocking posts to the API from non-white listed > apps? Since the DDOS attack we can't seem to send any posts th

[twitter-dev] Re: 401 Unauthorized...

I'm seeing some app problems this morning as well. Attempting to retrieve the timeline for the authenticated user returns no statuses. On Aug 12, 11:08 am, AccountingSoftwareGuy wrote: > Is Twitter still blocking posts to the API from non-white listed > apps?  Since the DDOS attack we can't see

[twitter-dev] Re: 401 Unauthorized

I think Twitter is still experiencing issues from this morning's DDOS attack. I've been working on code tonight and things were working swimmingly and now my app can't connect. On Aug 6, 8:38 pm, Goldbird wrote: > Are anyone experiencing "401 Unauthorized " errors? Everything worked > fine befo

[twitter-dev] Re: 401 Unauthorized When Getting an Access Token

oob means Out of Band, and is designed for desktop applications. If you don't specify a callback when getting the request token, you're given a pin to enter. It sounds like you're not using that flow though. On Sat, Aug 1, 2009 at 14:55, mattarnold1977 wrote: > > JDG, > > Thanks for the reply. I

[twitter-dev] Re: 401 Unauthorized When Getting an Access Token

JDG, Thanks for the reply. I didn't realize that I needed to include an oauth_callback parameter for getting the ACCESS TOKEN. I knew I could supply one (optional) when getting the REQUEST TOKEN. I thought it would automatically callback to the application I created with Twitter. I'm also not

[twitter-dev] Re: 401 Unauthorized When Getting an Access Token

Since you're not including an oauth_callback, i would assume you're using the oob flow, in which case, i have to ask, where's your oauth_verifier parameter? On Fri, Jul 31, 2009 at 13:09, mattarnold1977 wrote: > > Please, if anyone can assist I would be grateful. Here is a sample of > my url I'v

[twitter-dev] Re: 401 Unauthorized When Getting an Access Token

Please, if anyone can assist I would be grateful. Here is a sample of my url I've formed to get the access token: http://twitter.com/oauth/access_token?oauth_consumer_key=myconsumerkey&oauth_nonce=6475147&oauth_signature=mysignature&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1248981982&oau

[twitter-dev] Re: 401: Unauthorized application or token on friendship/exists

Well, I feel like a moron. Thanks for the help. Sorry to have asked you to spend time on something so ridiculously simple. On Apr 30, 11:04 am, Abraham Williams <4bra...@gmail.com> wrote: > friendships/exists.json > *not* > friendship/exists.json > > > > On Tue, Apr 28, 2009 at 11:06, tayknight

[twitter-dev] Re: 401: Unauthorized application or token on friendship/exists

statuses/followers.json *not* status/followers.json On Thu, Apr 30, 2009 at 01:47, app wrote: > > Getting the same problem for /status/followers.json > > Request for /verify/credentials.json works but not for /status/ > followers.json > > verify credentials header: > > GET /account/verify_creden

[twitter-dev] Re: 401: Unauthorized application or token on friendship/exists

friendships/exists.json *not* friendship/exists.json On Tue, Apr 28, 2009 at 11:06, tayknight wrote: > > I'm fairly sure I'm getting a proper token. Using the page > http://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.html I > get the same signature as in my failing url. > > GET looks l

[twitter-dev] Re: 401: Unauthorized application or token on friendship/exists

Getting the same problem for /status/followers.json Request for /verify/credentials.json works but not for /status/ followers.json verify credentials header: GET /account/verify_credentials.json? oauth_nonce=1867266443966123327&oauth_timestamp=1241073359&oauth_consumer_key=xKG4bNvaxBrHFD7tiLQA&

[twitter-dev] Re: 401 Unauthorized on OAuth calls?

Oh, On Fri, Apr 10, 2009 at 8:48 PM, Dominik Schwind wrote: ["body:protected"]=> > string(60) " �  sK��IMQ(�W(K��LI,IU�O,-�P(�L�K,)- ��٩y0y(�+" } That gibberish is just a gzip version of: string(43) "Failed to validate oauth signature or token" Thx, Dominik

[twitter-dev] Re: 401 Unauthorized on OAuth calls?

Hi, I'm seeing it on two applications "EagleTweet" and "EagleTweetDev" - I am using the Zend_OAuth library for PHP and I'm updating location fields for roughly 100 users with their FireEagle location once in a while. You can see it at http://eagletweet.com/ and I can give you the API Keys in priv

[twitter-dev] Re: 401 Unauthorized on OAuth calls?

Before opening an issue [1] it would have been nice to discuss. What are you trying to do? What steps have you taken to debug? Why do you think this is on our end and not a bug in your code? We can't help without knowing what's going on. 1. http://code.google.com/p/twitter-api/issues/detail?id=447

[twitter-dev] Re: 401 Unauthorized on OAuth calls?

I;ve created an issue,.. can you all comment there too? http://shortr.me/lz On Apr 10, 12:19 pm, Dominik Schwind wrote: > Hi everyone, > > since about half an hour ago I seem to be getting 401 Unauthorized > responses to my OAuth-ed API calls. > > Is that a known problem? > > Regards, > > Do

[twitter-dev] Re: 401 Unauthorized on OAuth calls?

Guys, Details are essential to help track down claims like these. What are you doing, and more importantly, how are you doing it? Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 10, 2009 at 6:48 AM, Bluespark wrote: > > Same here. > > On Apr 10, 10:19 pm, Dominik Schwind

[twitter-dev] Re: 401 Unauthorized on OAuth calls?

Same here. On Apr 10, 10:19 pm, Dominik Schwind wrote: > Hi everyone, > > since about half an hour ago I seem to be getting 401 Unauthorized > responses to my OAuth-ed API calls. > > Is that a known problem? > > Regards, > > Dominik