It's time to dig in and do some debugging, I guess. I'd start by examining the signature base strings, in client and server. Different signatures usually result from different signature base strings. In the Java client, place a breakpoint at the end of OAuthSignatureMethod.getSignature.
Using OAuth Core, a request body is not signed if it doesn't contain OAuth parameters. There's a draft extension for signing a request body http://groups.google.com/group/oauth-extensions/browse_thread/thread/113f52b3ccace4d7?hl=en but the Java library doesn't implement it. On Mar 17, 2:44 am, matthias <[email protected]> wrote: > However, my request never passes authentication on the server, > although I checked all parameters sent in a network log (I send them > in the HTTP header section) and they all look fine. We are using the > OAuth ruby gem on the server to authenticate requests (yes I know this > is probably beyond the scope of this group), but is there anything I > have to take care of when POSTing custom data to the server instead of > doing a GET? It works fine for all GET requests, so does the data I > send, but for POST requests it always seems to compute a different > signature than the client. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
