Hey Tom,

I think I am falling into this pitfall myself.  I don't have the users
information only the information that the iPhone twitter app sends me
for posting an image on a custom end point.  With that header
information they send should be enough to send back to twitter to get
the user information? Or am I not understanding the process of doing
this?

Thanks,
Shelby

On Sep 10, 4:18 pm, Tom van der Woerdt <i...@tvdw.eu> wrote:
> You don't need request_token for Echo - unless you don't have the user's
> credentials yet, but in that case you aren't using OAuth Echo.
>
> Tom
>
> On 9/11/10 1:13 AM, AS_Drone wrote:
>
>
>
> > We have been trying to implement the OAuth Echo method, but cannot get
> > a request-token. It returns with "Failed to validate oauth signature
> > and token".
>
> > Below is our Post data. Our signature aligns with data on the API
> > document. Any thoughts as to why we fail to oauth signature?
>
> > Post data:
>
> > Request Header:
> > POST /oauth/request_token HTTP/1.1
> > Content-Type: application/x-www-form-urlencoded
> > Authorization:
> > OAuth oauth_nonce="QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk",
> > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1272323042",
> > oauth_consumer_key="XXXXXXXXXXXXXXXXXX",
> > oauth_signature="Sr%2FKoecPb7D%2FnZNxt4qoM517Xjs%3D",
> > oauth_version="1.0"
> > Host: api.twitter.com
> > Content-Length: 0
> > Connection: Keep-Alive
> > Cache-Control: no-cache
> > Cookie: k=12.22.61.130.1283734903045073; guest_id=128373490305755705;
> > __utma=43838368.1906297211.1283734907.1283734907.1283762670.2;
> > __utmz=43838368.1283734907.1.1.utmcsr=(direct)|utmccn=(direct)|
> > utmcmd=(n
> > one); __utmv=43838368.lang%3A%20en; __qca=P0-1782216308-1283735015637;
> > __utmb=43838368.3.10.1283762670
> > Response Header:
> > HTTP/1.1 401 Unauthorized
> > Date: Mon, 06 Sep 2010 09:13:15 GMT
> > Server: hi
> > Status: 401 Unauthorized
> > X-Transaction: 1283764395-39211-63478
> > Last-Modified: Mon, 06 Sep 2010 09:13:15 GMT
> > X-Runtime: 0.00573
> > Content-Type: text/html; charset=utf-8
> > Content-Length: 44
> > Pragma: no-cache
> > X-Revision: DEV
> > Expires: Tue, 31 Mar 1981 05:00:00 GMT
> > Cache-Control: no-cache, no-store, must-revalidate, pre-check=0,
> > post-check=0
> > Set-Cookie:
> > _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCKEfUuYqAToHaWQiJWVhY2RjNDQ3NGNmMm
> > Mw%250ANjUwYWIzMGE3OWE4NDNlZTM3IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
> > %250A
> > OjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--
> > c7925282fe8f92e14b1a250c09ddff
> > e386a925be; domain=.twitter.com; path=/
> > Vary: Accept-Encoding
> > Connection: close
> > Failed to validate oauth signature and token

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Reply via email to