Fixed, thanks
On Oct 27, 10:00 am, angelsk wrote:
> I shall try creating another application - there are no other
> differences between the two scripts, other than the account.
>
> Thanks
>
> J
>
> On Oct 25, 4:02 pm, Taylor Singletary
> wrote:
>
>
>
> > If you create an alternate application wi
I shall try creating another application - there are no other
differences between the two scripts, other than the account.
Thanks
J
On Oct 25, 4:02 pm, Taylor Singletary
wrote:
> If you create an alternate application with the same account, issue access
> tokens for that account, and perform th
Please? No one sees a problem with the code?
On Sep 28, 7:20 pm, Rajendra Singh wrote:
> Hi BJ,
>
> Here is the complete code:
>
> include_once "oauth-php/library/OAuthStore.php";
> include_once "oauth-php/library/OAuthRequester.php";
>
> // register athttp://twitter.com/oauth_clientsand fill th
Hi BJ,
Here is the complete code:
include_once "oauth-php/library/OAuthStore.php";
include_once "oauth-php/library/OAuthRequester.php";
// register at http://twitter.com/oauth_clients and fill these two
define("TWITTER_CONSUMER_KEY", ""); // I removed this for this post
define("TWITTER_CONSUMER_
Are you certain that you're using the access token and secret received
and not the request token and secret?
Rajendra Singh wrote:
Help anyone?
On Sep 6, 7:16 pm, Rajendra Singh wrote:
Hi Tom,
Yes I did fill in those values correctly.
On Sep 6, 5:44 pm, Tom van der Woerdt wrote:
Help anyone?
On Sep 6, 7:16 pm, Rajendra Singh wrote:
> Hi Tom,
>
> Yes I did fill in those values correctly.
>
> On Sep 6, 5:44 pm, Tom van der Woerdt wrote:
>
> > On 9/6/10 10:57 PM, Rajendra Singh wrote:
>
> > > Hello,
>
> > > I took the "twoleggedtwitter.php" example file and added the follo
Hi Tom,
Yes I did fill in those values correctly.
On Sep 6, 5:44 pm, Tom van der Woerdt wrote:
> On 9/6/10 10:57 PM, Rajendra Singh wrote:
>
> > Hello,
>
> > I took the "twoleggedtwitter.php" example file and added the following
> > two lines:
>
> > $request = new OAuthRequester(TWITTER_UPDAT
Hi Taylor,
Ok, I'm new to this OAUTH thing. So if it doesn't support two-legged,
what do I use to authenticate?
Thanks.
On Sep 6, 6:12 pm, Taylor Singletary
wrote:
> Twitter doesn't support any two-legged OAuth operations at this time.
>
> Taylor
>
> On Mon, Sep 6, 2010 at 2:44 PM, Tom van der
I had a gaff in the bit of code that was parsing out the tokens in
Twitter's response, and for whatever reason these badly parsed tokens
worked just fine all the way up until a protected resource call. I'm
glad it's resolved, but I didn't enjoy going over my OAuth code in
excruciating detail a few
Fair enough. I'm most confused about the fact that moving from
request_token -> access_token doesn't want to use the
oauth_token_secret that comes with the initial unauthenticated request
token, in fact if I try to hash the signature with that it will fail.
I got over that and my implementation i
When my application had OAuth I was doing all of the requests using
OAuth in the headers and it worked fine... Perhaps you are experiencing
a transient issues. If you have never been able to make a protected
resource request there may be an error in your implementation.
Dimebrain wrote:
Ju
Just out of curiousity are you supporting the Authorization header
form of OAuth when making protected resource requests? I know they
work for tokens, but wondered if a call to verify_credentials for
instance needed to use parameters or if it could continue to use the
Authorization header?
On Mar
I found my problem.
My Authentication header information had an erroneous extra comma.
This was allowed when requesting the token, but not when exchanging
for the authorized token.
Removing the comma results in proper access_token retrieval.
On Mar 18, 7:27 pm, Dimebrain wrote:
> Hello,
>
> I
13 matches
Mail list logo
