Hi!
I'm at the fourth step of the OAuth Authorization Flow - trying to get the access token ( http://developer.yahoo.com/oauth/guide/oau...ccesstoken.html )
As I understand correctly, I generate new oauth_timestamp and new oauth_nonce for this request.

First of all I got the error saying that nonce is rejected. (oauth_problem=parameter_rejected&oauth_parameters_rejected=oauth_nonce)
I've noticed that I didn't separate it from oauth_timestamp with a '&' character (oauth_timestamp=1267265557oauth_nonce=1HXDM1DgOd). So wasn't separated oauth_timestamp from the string before it. I thought it to be strange that oauth_timestamp was accepted in first place...
I corrected the "error" so that timestamp and nonce looked like ...Tc5&oauth_timestamp=1267265855&oauth_nonce=cUeqO3ClED&oa...
Now, yahoo doesn't like my time stamp saying: oauth_problem=timestamp_refused&oauth_acceptable_timestamps=1267265257-1267266457 (and my timestamp IS in this range).
While I was in mood to play with it, I removed the separator of timestamp from the previous string: ...Tc5oauth_timestamp=1267266171&oauth_nonce=cUeqO3ClED&oa... Yahoo accepted my timestamp. But now I have another response: an html with title "OAuth error" telling me the following: "Invalid/used nonce".
I tried generating nonces with different lengths, I was comparing them: all different (at least among those generated by me).
I couldn't find what causes this response.

Will anyone tell me what is wrong with timestamp (why yahoo likes it when it's not separated and doesn't like it when it is) and what is wrong with the nonce?

Thank you!