You may want to use the OAuthBase.UrlEncode() method for this. I know 
that C# tends to use lowercase hex for values where OAuth prefers 
uppercase. This way, you know that the signature value being generated 
will match. (Yes, I realize that the values are also read opaquely and 
case doesn't matter, but it's also good to be consistent.)



rjlopes wrote:
> Hi,
>
> I was testing the OAuthBase and find out a bug when using it with
> MySpace.
>
> The problem is that MySpace uses an url as oauth_consumer_key and the
> NormalizeRequestParameters doesn't encode the parameters values.
>
> The fix is really simple, just change:
>
> sb.AppendFormat("{0}={1}", p.Name,p.Value);
>
> to:
>
> sb.AppendFormat("{0}={1}", p.Name, UrlEncode(p.Value));
>
> >
>
>   


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to