When the earlier developer posted, it wasn't possible to confirm that. In the time sense then we've resolved the issue, and the problem was with a faultily implemented method on our app's end.
Our use of GET versus POST on a POST-only API method, plus the method's false positive interpretation on the (actually error 401! ouf! ) return from the server = confusion. Thanks all, we're done and fixed here. On Apr 30, 12:12 pm, Abraham Williams <4bra...@gmail.com> wrote: > On Thu, Apr 30, 2009 at 04:31, CentralB-Dev <developm...@central-b.com>wrote: > > > > > We wonder if it might be a problem only with https requests and XML > > format or if others have this problem with http, JSON, and so on. > > You could easily test this yourself and know for sure. > > > > > > > We checked immediately, after several minutes, after several hours, > > and now after days. > > > Regards > > > On Apr 29, 3:50 pm, Nick Arnett <nick.arn...@gmail.com> wrote: > > > On Wed, Apr 29, 2009 at 12:41 PM, CentralB-Dev < > > developm...@central-b.com>wrote: > > > > > Although our app gets expected (successful) responses from both > > > > >https://twitter.com/friendships/create.xml?user_id=XXXX > > > > and > > > >https://twitter.com/friendships/create/XXXX.xml, > > > > > Neither actually follows (creates a friendship) successfully. > > > > Are you sure that this isn't just a cache issue... how are you checking > > to > > > see if the friendship exists? Did you check again after a while? > > > > Nick > > -- > Abraham Williams |http://the.hackerconundrum.com > Hacker |http://abrah.am|http://twitter.com/abraham > Web608 | Community Evangelist |http://web608.org > This email is: [ ] blogable [x] ask first [ ] private. > Sent from Madison, WI, United States
