René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"oauth_timestamp missing or invalid (suggestion for improvement with code)","articleBody":"According to https://oauth.net/core/1.0a/#nonce\r\n\r\n\u003e [...] the timestamp is expressed in the number of seconds since January 1, 1970 00:00:00 GMT [...]\r\n\r\nThe current implementation of `com.github.scribejava.core.services.TimestampServiceImpl.Timer.getMilis()` returns `System.currentTimeMillis();`.\r\nI think that this fulfills the specification only when the application runs in GMT time zone.\r\n\r\nMy application is running in Germany. And for a requests to a server my application got the answer \"oauth_timestamp missing or invalid\".\r\nIn the API docs there is a hint that \"[...] requests where the timestamp differs more than 10 minutes from the current UTC time will fail.\"\r\n\r\nChanging the implementation of `com.github.scribejava.core.services.TimestampServiceImpl.Timer.getMilis()` to `return Instant.now().getEpochSecond()*1000L;` works fine.\r\nSo I think that this should be the general implementation to have an oauth_timestamp independently from the system's time.","author":{"url":"https://github.com/fabst2w","@type":"Person","name":"fabst2w"},"datePublished":"2024-03-17T18:59:29.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1067/scribejava/issues/1067"}