Is that your full request? I don't see a Host: header, I don't see an
User-Agent header, etc.
Tom
On 9/14/10 6:53 PM, MTCoder wrote:
> thanks, that did the trick for reading the timeline. Now I'm having
> problems writing to the account.
> Any ideas?
>
> basestring:
> POST&http%3A%2F%2Fapi.twit
thanks, that did the trick for reading the timeline. Now I'm having
problems writing to the account.
Any ideas?
basestring:
POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml&
oauth_consumer_key%3Dx%26
oauth_nonce%3D444E51674F345149343D3D6A4D54304D%26
oauth_signa
Hi all,
Just for some public closure on the issue Jason and I found the
issue. It was related to some POST/GET changes that were needed to
make everything work.
Thanks;
— Matt
On Apr 9, 2009, at 09:47 AM, Jason Korkin wrote:
Yes, on my end it does.
On Thu, Apr 9, 2009 at 12:45 P
Yes, on my end it does.
On Thu, Apr 9, 2009 at 12:45 PM, Abraham Williams <4bra...@gmail.com> wrote:
> Does the consumer key/secret you are using still match what is on:
> https://twitter.com/oauth_clients?
>
>
> On Thu, Apr 9, 2009 at 11:30, Adam wrote:
>
>>
>> Same here. Moved to go the GET
Hi all,
I have yet to be able to reproduce this but that does not mean
there is no error. One thing that changed yesterday is the addition of
the "Woah there" page. That used to be a very ugly plain text 503 page
that said something like "invalid / unauthorized token" … we just made
i
Does the consumer key/secret you are using still match what is on:
https://twitter.com/oauth_clients?
On Thu, Apr 9, 2009 at 11:30, Adam wrote:
>
> Same here. Moved to go the GET method for requesting.
>
> Certain we are not re-using the same token.
>
> Still having problems ...
>
> On Apr 9, 9
Same here. Moved to go the GET method for requesting.
Certain we are not re-using the same token.
Still having problems ...
On Apr 9, 9:42 am, Jason Korkin wrote:
> Yeah quite certain we're not re-using the same token. We're using GET
> request.
>
>
>
> On Thu, Apr 9, 2009 at 10:30 AM, Mobas
Yeah quite certain we're not re-using the same token. We're using GET
request.
On Thu, Apr 9, 2009 at 10:30 AM, Mobasoft wrote:
>
> I too noticed some funky stuff this morning, but the authentication
> flow worked fine for me.
> What I did notice is that the verify_credentials.xml request is
I too noticed some funky stuff this morning, but the authentication
flow worked fine for me.
What I did notice is that the verify_credentials.xml request is now
forcing the use of GET (I had been using POST up until now).
Are you certain that you are not re-using the same AccessToken? If you
are,
I just went through the authentication flow with http://twitter.abrah.am and
it worked fine.
On Thu, Apr 9, 2009 at 09:11, Adam wrote:
>
> I too am having problems with OAuth.
>
> All of my keys have been de-authorized and I can't seem to re
> authenticate as well.
>
> On Apr 9, 8:36 am, Jason K
I too am having problems with OAuth.
All of my keys have been de-authorized and I can't seem to re
authenticate as well.
On Apr 9, 8:36 am, Jason Korkin wrote:
> Woke up this AM and went to check on a few things on our site... found that
> all of the oAuth keys had been de-authorized that we ha
11 matches
Mail list logo
