Hi Carlos:

Thanks for the sniplet. I just converted my source to encode when
*building* the parameter string and encode again when *adding* it.  I
tried on my proper app token codes and still signature error.

This is with my base looks like now.  NOTE: I changed the C++ source
back to the older tokens for this report since this is a public
newsgroup.  I kept the new 'dual' encoding in the source:

According to your pseudo code, my base is now:

POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
%2Fupdate.xml&oauth_consumer_key%3Dx80ZNISjmQ0Lxufp0QVM6w%26oauth_nonce
%3D6224761717242010000%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%3D1279401864%26oauth_token%3D63573892-
Y5GT47cl6ixaRKTaK5TpDg9N9D6g5Wqy718pIydjK%26oauth_version
%3D1.0%26status%3Dh

I did try to urlencode the status parameter, just to see but changed
it back to above.

And the new HTTP header (with signature):

Authorization: OAuth oauth_nonce="6224761717242010000",
oauth_signature_method="HMAC-SHA1", oauth_timestamp="1279401864",
oauth_consumer_key="x80ZNISjmQ0Lxufp0QVM6w", oauth_token="63573892-
Y5GT47cl6ixaRKTaK5TpDg9N9D6g5Wqy718pIydjK",
oauth_signature="nEOZNjNS0uyh58XzR2QH%2FPLK%2F7k%3D",
oauth_version="1.0"
Content-Type: application/x-www-form-urlencoded
Host: api.twitter.com
Content-Length: 10
Connection: Keep-Alive

What am I missing?

Vincent Collura
CeBeans

On Jul 17, 1:53 pm, Carlos <carlosju...@gmail.com> wrote:
> Are you doing this in PseudoCode?
>
> base = "method&URLEncode(endpoint)&URLEncode(URLParameterString)"
> where URLParameterString =
> "URLEncode(name)=URLEncode(value)&URLEncode(name)=URLEncode(value)..."
>
> On Jul 17, 11:01 am, CeBeans <inven...@cebeans.com> wrote:
>
> > Im developing a DLL in eVC++3.0 (native C++) that uses the Twitter
> > oAuth to update a status and have searched the web and support
> > websites for over a week but still cant figure the signature problem
> > out.
>
> > ====================================================================
> > NOTE: I have deleted the app in this example so Its safe to give out
> > the correct codes.  This way I can get a better response from support.
> > ====================================================================
>
> > The DLL is a simple call to update a users status: status=h (to get
> > this thing started)
>
> > My DELETED App Info:
> > ConsumerKey,"x80ZNISjmQ0Lxufp0QVM6w"
> > ConsumerSecret,"AHumtKUplfkqJVVy0VtbjoMROMU1SoVbCI8aIubu2Nc"
> > Token,"63573892-Y5GT47cl6ixaRKTaK5TpDg9N9D6g5Wqy718pIydjK"
> > TokenSecret,"6lRq2U4UoO3pv1Z0odU4lxhXvc3zlwJdOuyViQx44"
>
> > Signature Base:
> > POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
> > %2Fupdate.xml&oauth_consumer_key%3Dx80ZNISjmQ0Lxufp0QVM6w%26oauth_nonce
> > %3D40649761710562010000%26oauth_signature_method%3DHMAC-
> > SHA1%26oauth_timestamp%3D1279378609%26oauth_token%3D63573892-
> > Y5GT47cl6ixaRKTaK5TpDg9N9D6g5Wqy718pIydjK%26oauth_version
> > %3D1.0%26status%3Dh
>
> > Signature Key to Sign with:
> > AHumtKUplfkqJVVy0VtbjoMROMU1SoVbCI8aIubu2Nc&6lRq2U4UoO3pv1Z0odU4lxhXvc3zlwJdOuyViQx44
>
> > http Header:
> > =============
> > Authorization: OAuth oauth_nonce="40649761710562010000",
> > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1279378609",
> > oauth_consumer_key="x80ZNISjmQ0Lxufp0QVM6w", oauth_token="63573892-
> > Y5GT47cl6ixaRKTaK5TpDg9N9D6g5Wqy718pIydjK",
> > oauth_signature="ZztcjuTr1oxmVpQPAltfxiUEwEw%3D", oauth_version="1.0"
> > Content-Type: application/x-www-form-urlencoded
> > Host: api.twitter.com
> > Content-Length: 10
> > Connection: Keep-Alive
>
> > Http Footer
> > =============
> > status%3Dh
>
> > Server Response
> > ==============
> > <?xml version="1.0" encoding="UTF-8"?>
> > <hash>
> >   <request>/1/statuses/update.xml</request>
> >   <error>Incorrect signature</error>
> > </hash>
>
> > I also tried the HTTPS in the signature base, and still the same
> > error.  NOTE: The DLL callshttp://api.twitter.com/1/statuses/update.xml
>
> > Vincent Collura
> > CeBeans
>
>

Reply via email to