David, Back when I was writing the OAuth-PHP library I also bumped into this issue. At least the OAuth spec clearly defines how to encode, and there are test cases supplied.
You can check: http://www.marcworrell.com/article-2943-en.html For a discussion about the implications of RFC3986 usage in different languages. Greetings, Marc On 5 mei 2009, at 02:41, Zachary Voase wrote: > > Hi David, > > I found this to be an issue actually; in a shameless plug of my own > OAuth client library for Python, ZOAuth [1], I found that functions > like urllib.urlencode() were turning out URLs with '+' instead of the > (expected) '%20'. This is due to the presence of two functions: > urllib.quote() and urllib.quote_plus(); most of the urllib functions > use the latter, which was giving me hell because I was getting > signature errors from service providers and I couldn't understand why. > I basically solved it by copying the most frequently used urllib > functions straight from the stdlib, and rewriting them to use RFC3986 > encoding instead. Maybe you'd like to take a look at ZOAuth if this > turns out to be an issue for you. </plug> > > Regards, > Zack > > [1]: http://github.com/disturbyte/zoauth/ > > On May 4, 2:57 am, David W <d...@botanicus.net> wrote: >> Hi there, >> >> I see that OAuth 1.0 specifies RFC3986 URL encoding for parameters, >> but upon looking at the Python reference library I see that RFC2396 >> (aka. urllib.quote) encoding is used. Is this in error? >> >> The set of reserved characters differs in these specifications. >> >> Thanks, >> >> David. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oauth@googlegroups.com To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
