Chintanpan / oauth

Automatically exported from code.google.com/p/oauth
0 stars 0 forks source link

nonce timestamp returned when out of range returns in milliseconds not seconds JAVA #129

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Send invalid timestamp in seconds
2. Server returns invalid timestamp but states valid range in milliseconds
not seconds 

What is the expected output? What do you see instead?
The spec states that the time should be submitted in seconds and not
milliseconds but return error statement states milliseconds range as the
valid input.

What version of the product are you using? On what operating system?
Java, 20090531, Debian

Please provide any additional information below.
Server returns :
oauth_problem=timestamp_refused&oauth_acceptable_timestamps=1246561582853-124656
2182853
But I think it should return a valid timestamp like this :
oauth_problem=timestamp_refused&oauth_acceptable_timestamps=1246561582-124656218
2

Original issue reported on code.google.com by jsumme...@gmail.com on 5 Oct 2009 at 7:47

GoogleCodeExporter commented 9 years ago

Original comment by morten.f...@gmail.com on 5 Jan 2010 at 11:34

GoogleCodeExporter commented 9 years ago
fixed in -r1101

Original comment by jmkrist...@gmail.com on 24 May 2010 at 2:34