[oauth] Re: C# OAuthBase.cs bug
What I was refering was that the consumer key is an url in the case of
myspace and the OAuthBase internaly should urlencode that values on the
NormalizeRequestParameters method.
If I am not make myself clear enough please let me know and I will post an
example.
2009/7/17 jr conlin
>
> 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));
> >
> > >
> >
> >
>
>
> >
>
--
Ricardo Lopes
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[oauth] Re: C# OAuthBase.cs bug
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 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
-~--~~~~--~~--~--~---
[oauth] C# OAuthBase.cs bug
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 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
-~--~~~~--~~--~--~---
[oauth] RSA-SHA1 implementation for coldfusion (code for reference)
I worked on a coldfusion implementation of RSA-SHA1 signatures (calling java methods inside coldfusion itself). Posting it here, in case someone finds it useful, or if someone cares to embed in the code itself. Refine it, use it, do it... verified = #verifyFlag# --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
