Binary signatures must be base64 encoded and then percent encoded before transmission. Base64 encoding may produce a '+', which must then be percent encoded as %2B.
The Java OAuth library takes care of this if you use OAuthClient.invoke. But if you don't, you ordinarily must do the percent encoding yourself. This was discussed in http://groups.google.com/group/oauth/browse_thread/thread/6954bcaf46367ee1 Where might I find some documentation and/or source code, showing how 10gen fits together with OAuth? On Jan 8, 9:07 am, "Candide Kemmler" <[email protected]> wrote: > Sorry to interrupt an otherwise much higher-level discussion, but this issue > strikes me as something I may be facing just now. > > I noticed that signatures that contain '+'s are systematically rejected as > bad by plaxo (in this case). I'm using the java version of the library > (albeit from within 10gen). So is it bad? what should the +'s be replaced > with then? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
