[twitter-dev] Re: xAuth - favorites/create - bug - 401 error
Hi Taylor,
Thanks for the prompt reply
consumer key = vfM8qYNAEBfZsofKDNX65Q
consumer secret = fwBTEa4GRCPkszO26ma5mFLi1aInV82JTxJWbuL26g
token key = 13073932-seUruGITdpHxCJsoUhpjectP4hpdRubW62Q7nftyA
token secret = Y0cXVWuoymSiVRRhFMpCoHqQuJ2BxNSjRqotpRZx0
thanks
-chiu
On Jun 16, 12:35 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Can you share your signature base string that was used to create this
request?
I also highly recommending using HTTP Header-based OAuth instead of
query-string based OAuth. It separates concerns and makes debugging much
simpler.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Wed, Jun 16, 2010 at 11:44 AM, chiu ming luk lukchium...@gmail.comwrote:
The xAuth - favorites/create - is broken
I make calls to - favorites/create with an ID parameter using xAuth
$response = $connection-get ( 'favorites/create', array ('id' =
$status_id ) );
but I always getting 401 Not authorized Error
===
/1/favorites/create.json?
id=16170711730oauth_consumer_key=vfM8qYNAEBfZsofKDNX65Qoauth_nonce=bde7b35f5206ebc8a2cc31a7ea2b86acoauth_signature=V6%2BeC7%2FODp42W6GPV4EDWNpvSqY
%3Doauth_signature_method=HMAC-
SHA1oauth_timestamp=1276713005oauth_token=13073932-
seUruGITdpHxCJsoUhpjectP4hpdRubW62Q7nftyAoauth_version=1.0
===
On the other hand, The exact same request using Basic
Authentication, It will work fine. I either getting
- You have already favorited this status.
- Favorites added
Re: [twitter-dev] Re: xAuth - favorites/create - bug - 401 error
Hi Chiu,
You're going to want to reset your keys on your application settings on
dev.twitter.com -- we will really recommend not posting your consumer
secrets to the group -- but easy to rectify if you go and change your keys.
Your signature base string is actually a bit different than your keys. In
many OAuth libraries, they are difficult to access while other libraries
will make it easy. If you trace your code execution path through the OAuth
library you are using, you will find the step where your signature base
string is created -- that particular string holds most of the things that
can go wrong in an OAuth request.
Taylor
On Wed, Jun 16, 2010 at 12:53 PM, chiu ming luk lukchium...@gmail.comwrote:
Hi Taylor,
Thanks for the prompt reply
thanks
-chiu
On Jun 16, 12:35 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Can you share your signature base string that was used to create this
request?
I also highly recommending using HTTP Header-based OAuth instead of
query-string based OAuth. It separates concerns and makes debugging much
simpler.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Wed, Jun 16, 2010 at 11:44 AM, chiu ming luk lukchium...@gmail.com
wrote:
The xAuth - favorites/create - is broken
I make calls to - favorites/create with an ID parameter using xAuth
$response = $connection-get ( 'favorites/create', array ('id' =
$status_id ) );
but I always getting 401 Not authorized Error
===
/1/favorites/create.json?
id=16170711730oauth_consumer_key=vfM8qYNAEBfZsofKDNX65Qoauth_nonce=bde7b35f5206ebc8a2cc31a7ea2b86acoauth_signature=V6%2BeC7%2FODp42W6GPV4EDWNpvSqY
%3Doauth_signature_method=HMAC-
SHA1oauth_timestamp=1276713005oauth_token=13073932-
seUruGITdpHxCJsoUhpjectP4hpdRubW62Q7nftyAoauth_version=1.0
===
On the other hand, The exact same request using Basic
Authentication, It will work fine. I either getting
- You have already favorited this status.
- Favorites added
Re: [twitter-dev] Re: xAuth - favorites/create - bug - 401 error
favorites/create should be a POST. Try:
$response = $connection-post( 'favorites/create', array ('id' = $status_id
) );
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Wed, Jun 16, 2010 at 12:57, Taylor Singletary
taylorsinglet...@twitter.com wrote:
Hi Chiu,
You're going to want to reset your keys on your application settings on
dev.twitter.com -- we will really recommend not posting your consumer
secrets to the group -- but easy to rectify if you go and change your keys.
Your signature base string is actually a bit different than your keys. In
many OAuth libraries, they are difficult to access while other libraries
will make it easy. If you trace your code execution path through the OAuth
library you are using, you will find the step where your signature base
string is created -- that particular string holds most of the things that
can go wrong in an OAuth request.
Taylor
On Wed, Jun 16, 2010 at 12:53 PM, chiu ming luk lukchium...@gmail.comwrote:
Hi Taylor,
Thanks for the prompt reply
thanks
-chiu
On Jun 16, 12:35 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Can you share your signature base string that was used to create this
request?
I also highly recommending using HTTP Header-based OAuth instead of
query-string based OAuth. It separates concerns and makes debugging much
simpler.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Wed, Jun 16, 2010 at 11:44 AM, chiu ming luk lukchium...@gmail.com
wrote:
The xAuth - favorites/create - is broken
I make calls to - favorites/create with an ID parameter using xAuth
$response = $connection-get ( 'favorites/create', array ('id' =
$status_id ) );
but I always getting 401 Not authorized Error
===
/1/favorites/create.json?
id=16170711730oauth_consumer_key=vfM8qYNAEBfZsofKDNX65Qoauth_nonce=bde7b35f5206ebc8a2cc31a7ea2b86acoauth_signature=V6%2BeC7%2FODp42W6GPV4EDWNpvSqY
%3Doauth_signature_method=HMAC-
SHA1oauth_timestamp=1276713005oauth_token=13073932-
seUruGITdpHxCJsoUhpjectP4hpdRubW62Q7nftyAoauth_version=1.0
===
On the other hand, The exact same request using Basic
Authentication, It will work fine. I either getting
- You have already favorited this status.
- Favorites added
[twitter-dev] Re: xAuth - favorites/create - bug - 401 error
If I do a HTTP POST - i got error message saying that
This method requires a GET.
On Jun 16, 1:00 pm, Abraham Williams 4bra...@gmail.com wrote:
favorites/create should be a POST. Try:
$response = $connection-post( 'favorites/create', array ('id' = $status_id
) );
Abraham
-
Abraham Williams | Hacker Advocate |http://abrah.am
@abraham |http://projects.abrah.am|http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Wed, Jun 16, 2010 at 12:57, Taylor Singletary
taylorsinglet...@twitter.com wrote:
Hi Chiu,
You're going to want to reset your keys on your application settings on
dev.twitter.com -- we will really recommend not posting your consumer
secrets to the group -- but easy to rectify if you go and change your keys.
Your signature base string is actually a bit different than your keys. In
many OAuth libraries, they are difficult to access while other libraries
will make it easy. If you trace your code execution path through the OAuth
library you are using, you will find the step where your signature base
string is created -- that particular string holds most of the things that
can go wrong in an OAuth request.
Taylor
On Wed, Jun 16, 2010 at 12:53 PM, chiu ming luk
lukchium...@gmail.comwrote:
Hi Taylor,
Thanks for the prompt reply
thanks
-chiu
On Jun 16, 12:35 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Can you share your signature base string that was used to create this
request?
I also highly recommending using HTTP Header-based OAuth instead of
query-string based OAuth. It separates concerns and makes debugging much
simpler.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Wed, Jun 16, 2010 at 11:44 AM, chiu ming luk lukchium...@gmail.com
wrote:
The xAuth - favorites/create - is broken
I make calls to - favorites/create with an ID parameter using xAuth
$response = $connection-get ( 'favorites/create', array ('id' =
$status_id ) );
but I always getting 401 Not authorized Error
===
/1/favorites/create.json?
id=16170711730oauth_consumer_key=vfM8qYNAEBfZsofKDNX65Qoauth_nonce=bde7b35f5206ebc8a2cc31a7ea2b86acoauth_signature=V6%2BeC7%2FODp42W6GPV4EDWNpvSqY
%3Doauth_signature_method=HMAC-
SHA1oauth_timestamp=1276713005oauth_token=13073932-
seUruGITdpHxCJsoUhpjectP4hpdRubW62Q7nftyAoauth_version=1.0
===
On the other hand, The exact same request using Basic
Authentication, It will work fine. I either getting
- You have already favorited this status.
- Favorites added
[twitter-dev] Re: xAuth - favorites/create - bug - 401 error
The signature base string is the following
zZyk1NxKlpXZEapSszao6PCIAQM=
$signature = $this-build_signature($signature_method, $consumer,
$token);
thanks
-chiu
On Jun 16, 12:57 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Chiu,
You're going to want to reset your keys on your application settings on
dev.twitter.com -- we will really recommend not posting your consumer
secrets to the group -- but easy to rectify if you go and change your keys.
Your signature base string is actually a bit different than your keys. In
many OAuth libraries, they are difficult to access while other libraries
will make it easy. If you trace your code execution path through the OAuth
library you are using, you will find the step where your signature base
string is created -- that particular string holds most of the things that
can go wrong in an OAuth request.
Taylor
On Wed, Jun 16, 2010 at 12:53 PM, chiu ming luk lukchium...@gmail.comwrote:
Hi Taylor,
Thanks for the prompt reply
thanks
-chiu
On Jun 16, 12:35 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Can you share your signature base string that was used to create this
request?
I also highly recommending using HTTP Header-based OAuth instead of
query-string based OAuth. It separates concerns and makes debugging much
simpler.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Wed, Jun 16, 2010 at 11:44 AM, chiu ming luk lukchium...@gmail.com
wrote:
The xAuth - favorites/create - is broken
I make calls to - favorites/create with an ID parameter using xAuth
$response = $connection-get ( 'favorites/create', array ('id' =
$status_id ) );
but I always getting 401 Not authorized Error
===
/1/favorites/create.json?
id=16170711730oauth_consumer_key=vfM8qYNAEBfZsofKDNX65Qoauth_nonce=bde7b35f5206ebc8a2cc31a7ea2b86acoauth_signature=V6%2BeC7%2FODp42W6GPV4EDWNpvSqY
%3Doauth_signature_method=HMAC-
SHA1oauth_timestamp=1276713005oauth_token=13073932-
seUruGITdpHxCJsoUhpjectP4hpdRubW62Q7nftyAoauth_version=1.0
===
On the other hand, The exact same request using Basic
Authentication, It will work fine. I either getting
- You have already favorited this status.
- Favorites added
[twitter-dev] Re: xAuth - favorites/create - bug - 401 error
Request =
/1/favorites/create.json?
id=16170711730oauth_consumer_key=vfM8qYNAEBfZsofKDNX65Qoauth_nonce=6c2b0e1a7af3dd0b60680c8860e63454oauth_signature=zZyk1NxKlpXZEapSszao6PCIAQM
%3Doauth_signature_method=HMAC-
SHA1oauth_timestamp=1276724507oauth_token=13073932-
seUruGITdpHxCJsoUhpjectP4hpdRubW62Q7nftyAoauth_version=1.0
signature base string =
zZyk1NxKlpXZEapSszao6PCIAQM=
$signature = $this-build_signature($signature_method, $consumer,
$token);
thanks
-chiu
On Jun 16, 12:57 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Chiu,
You're going to want to reset your keys on your application settings on
dev.twitter.com -- we will really recommend not posting your consumer
secrets to the group -- but easy to rectify if you go and change your keys.
Your signature base string is actually a bit different than your keys. In
many OAuth libraries, they are difficult to access while other libraries
will make it easy. If you trace your code execution path through the OAuth
library you are using, you will find the step where your signature base
string is created -- that particular string holds most of the things that
can go wrong in an OAuth request.
Taylor
On Wed, Jun 16, 2010 at 12:53 PM, chiu ming luk lukchium...@gmail.comwrote:
Hi Taylor,
Thanks for the prompt reply
thanks
-chiu
On Jun 16, 12:35 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Can you share your signature base string that was used to create this
request?
I also highly recommending using HTTP Header-based OAuth instead of
query-string based OAuth. It separates concerns and makes debugging much
simpler.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Wed, Jun 16, 2010 at 11:44 AM, chiu ming luk lukchium...@gmail.com
wrote:
The xAuth - favorites/create - is broken
I make calls to - favorites/create with an ID parameter using xAuth
$response = $connection-get ( 'favorites/create', array ('id' =
$status_id ) );
but I always getting 401 Not authorized Error
===
/1/favorites/create.json?
id=16170711730oauth_consumer_key=vfM8qYNAEBfZsofKDNX65Qoauth_nonce=bde7b35f5206ebc8a2cc31a7ea2b86acoauth_signature=V6%2BeC7%2FODp42W6GPV4EDWNpvSqY
%3Doauth_signature_method=HMAC-
SHA1oauth_timestamp=1276713005oauth_token=13073932-
seUruGITdpHxCJsoUhpjectP4hpdRubW62Q7nftyAoauth_version=1.0
===
On the other hand, The exact same request using Basic
Authentication, It will work fine. I either getting
- You have already favorited this status.
- Favorites added
Re: [twitter-dev] Re: xAuth - favorites/create - bug - 401 error
Let us continue this on the issue tracker so we don't spam the list as
much: http://github.com/abraham/twitteroauth/issues#issue/33
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Wed, Jun 16, 2010 at 14:42, chiu ming luk lukchium...@gmail.com wrote:
The signature base string is the following
zZyk1NxKlpXZEapSszao6PCIAQM=
$signature = $this-build_signature($signature_method, $consumer,
$token);
thanks
-chiu
On Jun 16, 12:57 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Chiu,
You're going to want to reset your keys on your application settings on
dev.twitter.com -- we will really recommend not posting your consumer
secrets to the group -- but easy to rectify if you go and change your
keys.
Your signature base string is actually a bit different than your keys. In
many OAuth libraries, they are difficult to access while other libraries
will make it easy. If you trace your code execution path through the
OAuth
library you are using, you will find the step where your signature base
string is created -- that particular string holds most of the things that
can go wrong in an OAuth request.
Taylor
On Wed, Jun 16, 2010 at 12:53 PM, chiu ming luk lukchium...@gmail.com
wrote:
Hi Taylor,
Thanks for the prompt reply
thanks
-chiu
On Jun 16, 12:35 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Can you share your signature base string that was used to create this
request?
I also highly recommending using HTTP Header-based OAuth instead of
query-string based OAuth. It separates concerns and makes debugging
much
simpler.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Wed, Jun 16, 2010 at 11:44 AM, chiu ming luk
lukchium...@gmail.com
wrote:
The xAuth - favorites/create - is broken
I make calls to - favorites/create with an ID parameter using
xAuth
$response = $connection-get ( 'favorites/create', array ('id' =
$status_id ) );
but I always getting 401 Not authorized Error
===
/1/favorites/create.json?
id=16170711730oauth_consumer_key=vfM8qYNAEBfZsofKDNX65Qoauth_nonce=bde7b35f5206ebc8a2cc31a7ea2b86acoauth_signature=V6%2BeC7%2FODp42W6GPV4EDWNpvSqY
%3Doauth_signature_method=HMAC-
SHA1oauth_timestamp=1276713005oauth_token=13073932-
seUruGITdpHxCJsoUhpjectP4hpdRubW62Q7nftyAoauth_version=1.0
===
On the other hand, The exact same request using Basic
Authentication, It will work fine. I either getting
- You have already favorited this status.
- Favorites added
Re: [twitter-dev] Re: xAuth - favorites/create - bug - 401 error
The URL to create a favorite using the API is a POST to:
/1/favorites/create/id.format
So in your case it would be:
/1/favorites/create/16170711730.json
Give that a try and let us know how it goes. I know the docs on
dev.twitter.com are incorrect for this so i'll be updating them soon.
On Wed, Jun 16, 2010 at 2:46 PM, chiu ming luk lukchium...@gmail.comwrote:
Request =
/1/favorites/create.json?
id=16170711730oauth_consumer_key=vfM8qYNAEBfZsofKDNX65Qoauth_nonce=6c2b0e1a7af3dd0b60680c8860e63454oauth_signature=zZyk1NxKlpXZEapSszao6PCIAQM
%3Doauth_signature_method=HMAC-
SHA1oauth_timestamp=1276724507oauth_token=13073932-
seUruGITdpHxCJsoUhpjectP4hpdRubW62Q7nftyAoauth_version=1.0
signature base string =
zZyk1NxKlpXZEapSszao6PCIAQM=
$signature = $this-build_signature($signature_method, $consumer,
$token);
thanks
-chiu
On Jun 16, 12:57 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Chiu,
You're going to want to reset your keys on your application settings on
dev.twitter.com -- we will really recommend not posting your consumer
secrets to the group -- but easy to rectify if you go and change your
keys.
Your signature base string is actually a bit different than your keys. In
many OAuth libraries, they are difficult to access while other libraries
will make it easy. If you trace your code execution path through the
OAuth
library you are using, you will find the step where your signature base
string is created -- that particular string holds most of the things that
can go wrong in an OAuth request.
Taylor
On Wed, Jun 16, 2010 at 12:53 PM, chiu ming luk lukchium...@gmail.com
wrote:
Hi Taylor,
Thanks for the prompt reply
thanks
-chiu
On Jun 16, 12:35 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Can you share your signature base string that was used to create this
request?
I also highly recommending using HTTP Header-based OAuth instead of
query-string based OAuth. It separates concerns and makes debugging
much
simpler.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Wed, Jun 16, 2010 at 11:44 AM, chiu ming luk
lukchium...@gmail.com
wrote:
The xAuth - favorites/create - is broken
I make calls to - favorites/create with an ID parameter using
xAuth
$response = $connection-get ( 'favorites/create', array ('id' =
$status_id ) );
but I always getting 401 Not authorized Error
===
/1/favorites/create.json?
id=16170711730oauth_consumer_key=vfM8qYNAEBfZsofKDNX65Qoauth_nonce=bde7b35f5206ebc8a2cc31a7ea2b86acoauth_signature=V6%2BeC7%2FODp42W6GPV4EDWNpvSqY
%3Doauth_signature_method=HMAC-
SHA1oauth_timestamp=1276713005oauth_token=13073932-
seUruGITdpHxCJsoUhpjectP4hpdRubW62Q7nftyAoauth_version=1.0
===
On the other hand, The exact same request using Basic
Authentication, It will work fine. I either getting
- You have already favorited this status.
- Favorites added
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
[twitter-dev] Re: xAuth - favorites/create - bug - 401 error
Yes, you are right,
abraham mention that the following will fix the problem
$response = $connection-post('favorites/create/' . $status_id);
-chiu
On Jun 16, 2:51 pm, Matt Harris thematthar...@twitter.com wrote:
The URL to create a favorite using the API is a POST to:
/1/favorites/create/id.format
So in your case it would be:
/1/favorites/create/16170711730.json
Give that a try and let us know how it goes. I know the docs on
dev.twitter.com are incorrect for this so i'll be updating them soon.
On Wed, Jun 16, 2010 at 2:46 PM, chiu ming luk lukchium...@gmail.comwrote:
Request =
/1/favorites/create.json?
id=16170711730oauth_consumer_key=vfM8qYNAEBfZsofKDNX65Qoauth_nonce=6c2b0e1a7af3dd0b60680c8860e63454oauth_signature=zZyk1NxKlpXZEapSszao6PCIAQM
%3Doauth_signature_method=HMAC-
SHA1oauth_timestamp=1276724507oauth_token=13073932-
seUruGITdpHxCJsoUhpjectP4hpdRubW62Q7nftyAoauth_version=1.0
signature base string =
zZyk1NxKlpXZEapSszao6PCIAQM=
$signature = $this-build_signature($signature_method, $consumer,
$token);
thanks
-chiu
On Jun 16, 12:57 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Chiu,
You're going to want to reset your keys on your application settings on
dev.twitter.com -- we will really recommend not posting your consumer
secrets to the group -- but easy to rectify if you go and change your
keys.
Your signature base string is actually a bit different than your keys. In
many OAuth libraries, they are difficult to access while other libraries
will make it easy. If you trace your code execution path through the
OAuth
library you are using, you will find the step where your signature base
string is created -- that particular string holds most of the things that
can go wrong in an OAuth request.
Taylor
On Wed, Jun 16, 2010 at 12:53 PM, chiu ming luk lukchium...@gmail.com
wrote:
Hi Taylor,
Thanks for the prompt reply
thanks
-chiu
On Jun 16, 12:35 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Can you share your signature base string that was used to create this
request?
I also highly recommending using HTTP Header-based OAuth instead of
query-string based OAuth. It separates concerns and makes debugging
much
simpler.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Wed, Jun 16, 2010 at 11:44 AM, chiu ming luk
lukchium...@gmail.com
wrote:
The xAuth - favorites/create - is broken
I make calls to - favorites/create with an ID parameter using
xAuth
$response = $connection-get ( 'favorites/create', array ('id' =
$status_id ) );
but I always getting 401 Not authorized Error
===
/1/favorites/create.json?
id=16170711730oauth_consumer_key=vfM8qYNAEBfZsofKDNX65Qoauth_nonce=bde7b35f5206ebc8a2cc31a7ea2b86acoauth_signature=V6%2BeC7%2FODp42W6GPV4EDWNpvSqY
%3Doauth_signature_method=HMAC-
SHA1oauth_timestamp=1276713005oauth_token=13073932-
seUruGITdpHxCJsoUhpjectP4hpdRubW62Q7nftyAoauth_version=1.0
===
On the other hand, The exact same request using Basic
Authentication, It will work fine. I either getting
- You have already favorited this status.
- Favorites added
--
Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris
