[twitter-dev] Re: OAuth and twitter.com home authentication strange behavior

[Andreu Pere]

The same behaviour for my application. When the app wants to start the oAuth
workflow in order to authenticate and login the user, the server returns a
timeout from https://twitter.com/oauth/authenticate?parameters

On Thu, Aug 6, 2009 at 11:24 PM, Rich rhyl...@gmail.com wrote:


 I can't get oAuth to authenticate on any of my clients either.  It
 works when the client has previously authenticated... but trying to
 get a new token it fails when clicking 'Allow'

 On Aug 6, 7:42 pm, stephane stephane.philipa...@gmail.com wrote:
  It's probably linked to the current DDOS but the authentication flow
  shows some strange behavior :
 
  1 - I try to initiate an OAuth authentication fromwww.twazzup.com
- twazzup server gets a timeout trying to connect to twitter for
  oauth token (ApplicationError 5 on appengine)
  3 - I go to twitter.com click sign-in
- strangely twitter redirects me to the oauth authorization form
  (do you want to allow twazzup blabla ...)
 
  So I have to questions there :
  A / did you block incoming OAuth reqs from appengine ?
  B/ is the strange behavior (twitter home authentication mixing with
  another OAuth flow) something we, 3rd party app developers, can or
  should take care of ?
 
  Cheers,
 
  Stephanewww.twazzup.com

[twitter-dev] Re: twitter api server seems to be down (getting invalid signature) since 5.15 pm pst

[Andreu Pere]

Oh yes!!! The methods which didn't work were sent by plain HTTP and the
other methods that work ok were using HTTPS didn't mind!!

Now, all methods are working on HTTPS, and all are working properly!! Sure,
it seams the solution is use HTTPS

Thanks!!

On Thu, Jul 30, 2009 at 10:16 PM, AlbertC compl...@gmail.com wrote:


 I don't know if this will help at all, but I had the same
 problem...after hours spent on this stupid error, I realized that some
 of my request URLs were using http, and some https.
 After changing all the request URLs to https, everything's working
 perfectly (I'm using exactly the same client library). It does make
 all kinds of sense.

 Regular http requests worked fine before, though.

 It's probably been mentioned before. If so, I missed it, sorry. :)

 On Jul 30, 12:03 pm, Andreu andreup...@gmail.com wrote:
  I read this discussion carefully and I cannot extract a conclusion...
 
  The question is why a set of API methods are working and others aren't
  working properly, returning a 'Incorrect signature' error.
 
  Methods working now:
  - posting a tweet (statuses/update). Works fine
  - extract user timeline (statuses/user_timeline). Works fine either
  the request is made by the authenticated user (user requesting his own
  timeline) or requesting a 3rd user timeline
  - verify credentials (account/verify_credentials). Works fine.
 
  Methods not working:
  - delete a tweet (statuses/destroy).
  - destroy a relationship (friendships/destroy)
  - create a relationship (friendships/create)
  - extract friends timeline (statuses/friends_timeline)
 
  All methods are relying over the same base python method, building the
  same requests changing the API urls and/or parameters... The library I
  am using ishttp://oauth.googlecode.com/svn/code/python/oauth/oauth.py
 
  I think if server signature verification have been modified, and now
  is running 'properly', all my methods should fail, especially the
  methods that authentication is required... but the problem is ones are
  working and others not working.