tags:

views:

486

answers:

2

Ive been battling with the oAuth flow for a while with my twitter app. I finally got my access token granted, and now i cant call the twitter update url without getting an 'invalid nonce' error, yet im building and signing the URL in the exact same way as when calling the request and access token methods. Has anyone else had this problem, and do you know how to solve it??

+1  A: 

Ok so i figured out that query strings get cut off after a certain length. So instead of using a web client to do all my work, i switched to web request and used the 'content' for the parameters instead, this appears to have fixed the problem!

xoxo
A: 

Can you explain a little bit more about how you solved this problem as i am stuck on the same problem.

Thanks, Rahul

Rahul Juneja