[oauth] Re: 400 Bad Request?

2010-03-02 Thread John Kristian
To control the oauth_timestamp, pass it to the Java library as a parameter. There are several ways to do this. You can pass it to OAuthClient methods as a parameter; for example client.getRequestToken(accessor, OAuthMessage.GET, OAuth.newList("oauth_timestamp", yourValue)). You can override OAut

[oauth] Re: 400 Bad Request?

2010-02-26 Thread Mark
Hi all, Sorry I'm still not understanding - I'm using the client java library from this project out of the box. So it seems to send across a timestamp taken from the system clock, which reflects whatever time zone the user's device is set to. What are my options in this case? One is to tell all my

Re: [oauth] Re: 400 Bad Request?

2010-02-26 Thread Vinod facebook
Yes, even I faced timestamp validation issues initially and when I changed my clock settings, it began to work fine. On Fri, Feb 26, 2010 at 3:49 AM, John Kristian wrote: > The oauth_timestamp has no time zone; it's implicitly Universal Time > (also known as GMT). But OAuth service providers usu

[oauth] Re: 400 Bad Request?

2010-02-25 Thread John Kristian
The oauth_timestamp has no time zone; it's implicitly Universal Time (also known as GMT). But OAuth service providers usually require consumers' clocks to be fairly accurate. You could try implementing your client to adapt to the server's clock. It could look at the Date in the HTTP response heade

[oauth] Re: 400 Bad Request?

2010-02-21 Thread Mark
Hi Vinod, I don't understand this though - the PC requesting the oauth service is just a regular user - I can't expect them to have their timezone set to be the same as the server? The server is using eastern standard time. There must be some way around this issue, otherwise all oauth services woul

Re: [oauth] Re: 400 Bad Request?

2010-02-20 Thread Vinod facebook
Hi dj, The timestamp refused error occurs due to the mismatch of time between your server and the consumer's server. You need to synchronize the PC clock in accordance. With Regards, R.Vinod Kumar On Fri, Feb 19, 2010 at 12:35 AM, dj wrote: > Hi Robert, > > Thanks for the information.

[oauth] Re: 400 Bad Request?

2010-02-18 Thread dj
and if I am reading this right, it looks like the oauth client library is passing in a timestamp of: 1266530170 while the server is saying it must be between: 1266519077-1266519677 to be acceptable. This is confusing to me, I'm not sure where I would fix this, is that a problem with the ser

[oauth] Re: 400 Bad Request?

2010-02-18 Thread dj
Hi Robert, Thanks for the information. I do get some information printed from the caught OAuthProblemException. It is printed below. Looks like something related to the timestamp being refused? I tried searching for the timestamp refused error, and it seems like you're supposed to be setting the c