[twitter-dev] Re: Potential Solution To OAuth Problem
Sorry, no. I'm using rawurlencode in PHP, which encodes %20 still failing. // snip $key = rawurlencode($this-consumer_secret).''.rawurlencode($this- token_secret); $this-args['oauth_signature'] = base64_encode( hash_hmac( 'sha1', $str, $key, true ) ); // snip
[twitter-dev] Re: Potential Solution To OAuth Problem
The + - %20 solution seems to work for me. I am writing my own OAuth library in Java, and java.net.URLEncoder encodes the space character to +. There could be a better way, but replacing the resulted + with %20, status update on Twitter now seems to work.
[twitter-dev] Re: Potential Solution To OAuth Problem
You shouldn't use java.net.URLEncoder as it encodes more characters than the OAuth spec specifies should be encoded. On Tue, Jul 28, 2009 at 14:12, ks91 ks91...@gmail.com wrote: The + - %20 solution seems to work for me. I am writing my own OAuth library in Java, and java.net.URLEncoder encodes the space character to +. There could be a better way, but replacing the resulted + with %20, status update on Twitter now seems to work. -- Internets. Serious business.
[twitter-dev] Re: Potential Solution To OAuth Problem
Check this thread for a solution for VB.NET libraries (and perhaps a good starting point for other languages). http://groups.google.com/group/twitter-development-talk/browse_thread/thread/734a29fd71d7fdd9# On Jul 28, 8:19 pm, JDG ghil...@gmail.com wrote: You shouldn't use java.net.URLEncoder as it encodes more characters than the OAuth spec specifies should be encoded. On Tue, Jul 28, 2009 at 14:12, ks91 ks91...@gmail.com wrote: The + - %20 solution seems to work for me. I am writing my own OAuth library in Java, and java.net.URLEncoder encodes the space character to +. There could be a better way, but replacing the resulted + with %20, status update on Twitter now seems to work. -- Internets. Serious business.
[twitter-dev] Re: Potential Solution To OAuth Problem
This may solve your problem, but it doesn't work for me. I am getting errors for API calls that have no spaces, such as create friend, destroy, etc.
[twitter-dev] Re: Potential Solution To OAuth Problem
Dang, sorry. Create is working for me. There are almost certainly other differences in the encoding between HttpUtility.URLEncode and HttpUtility.UrlPathEncode. Is your library written in .NET? If so, can you change the encoding on the requests that are failing to see if it fixes the issue for you? On Jul 28, 1:29 am, chinaski007 chinaski...@gmail.com wrote: This may solve your problem, but it doesn't work for me. I am getting errors for API calls that have no spaces, such as create friend, destroy, etc.
[twitter-dev] Re: Potential Solution To OAuth Problem
Using Perl libraries. Will mess around and see what I can do. Super annoying.