That explains it.
I stopped using my phone during the holiday break, and after that, nothing
worked.
I typically send the mentions.json with the count, since_id and max_id
parameters, but over the holidays that accumulated and started returning
errors. I heard about this problem first from a
Hello folks,
My twitter client (TweetStation for the iPhone) broke during the
holidays as twitter now sends me back a 502 Bad Gateway error when I post
the following:
GET /1/statuses/mentions.json?count=200 HTTP/1.1
authorization: [My Oauth goes here]
Host: api.twitter.com
I am doing t
Hello guys,
Perhaps the most frustrating piece in dealing with the OAuth
configuration is that the twitter OAuth page talks casually about
"urlEncode". You need to "urlEncode this" and "urlEncode that". What
the page does not say is that "urlEncode" is not a standard
urlEncoding system that
Hello,
> 1) You do not oAuth sign the actual request toTwitPic
> 2) You make a fake request to Twitter's verify credentials api over
> SSL and grab the Authorization header that would be sent, however when
> you create the header make sure you include a 'Realm'
> ofhttps://api.twitter.com
> 3) Cr
Hello,
I figured this out, it was my fault, the bug was not really the
extra parameters, but an early optimization on the reuse of the SHA1
code.
Miguel.
On May 21, 5:19 pm, Miguel de Icaza wrote:
> Hello,
>
> I was able to make progress for my original sample (?count=200)
&
Hello,
I was able to make progress for my original sample (?count=200)
but I am running into a different problem when I pass more than one
parameter, in this case &count=200&since_id=NNN
I did sort the parameters as suggested by Dana from the query
string, here is my result:
"GET&http%
t;
> Hope this helps!
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
>
> On Fri, May 21, 2010 at 9:59 AM, Miguel de Icaza
> wrote:
>
>
>
> > Hello folks,
>
> > I have my client speaking OAuth to twitter for the enti
Hello folks,
I have my client speaking OAuth to twitter for the entire initial
dance up to getting my access token.
But once I try using the access token to call:
http://api.twitter.com/1/statuses/mentions.json?count=200
All I get from twitter is a 401 with the following body:
{"req
