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

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,

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

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

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:

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

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

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

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

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

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

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