The signature should be generated for every single request to the Twitter API. It is based on your request URL and parameters.
You can read a detailed explanation here http://tools.ietf.org/html/draft-hammer-oauth-08#page-19. Abraham On Fri, Jan 22, 2010 at 11:11, eco_bach <bac...@gmail.com> wrote: > Hi > My OAuth sign In process is failing to verify my signature, so I > thought I should at least ensure I understand the meaning of the term. > > Every time my web application launches, it generates a unique > signature, which doesn't change for the current session. > ie, if I quit the application, then restart, a new signature is > generated. > > This signature should be appended to the end of > my initial request token request > my access token request > my verify credentials request > and my status update requests. > > Am I correct in the above? > -- Abraham Williams | Moved to Seattle | May cause email delays Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States