Looks like it's working perfectly now. Thanks guys. -Isaac
On Apr 14, 11:53 am, Matt Sanford <m...@twitter.com> wrote: > Hey Abraham, > > Checkout the dreaded issue 433 as we found out there is a bug in > that RESERVED_CHARACTERS depending on the $KCODE variable. > > Thanks; > — Matt > > On Apr 14, 2009, at 11:35 AM, Abraham Williams wrote: > > > I'll try to have a look at this tonight. > > > Abraham > > > On Fri, Apr 10, 2009 at 19:02, Matt Sanford <m...@twitter.com> wrote: > > Hi Isaac, > > > The change we implemented seems to have fixed people using a > > newer version of the Ruby oauth gem but it sounds like it may have > > broken some other libraries. My guess is that there is an encoding > > normalization difference between the PHP library and the newest Ruby > > version right NOW. The spec does have some normalization information > > [1] [2] and it seems like the Ruby code is doing that work via [3]: > > > def escape(value) > > URI::escape(value.to_s, OAuth::RESERVED_CHARACTERS) > > end > > > And that constant is defined as: > > > # reserved character regexp, per section 5.1 > > RESERVED_CHARACTERS = /[^\w\d\-\.\_\~]/ > > > I know Abraham reads this Google Group so perhaps he and I can > > get together on Monday and compare some pre-signature strings > > between Ruby and PHP to figure out what's going on. If you see this > > Abraham drop me an email otherwise you can expect one from me on > > Monday to sort this out. > > > Thanks; > > — Matt > > > [1] -http://oauth.net/core/1.0/#anchor14 > > [2] -http://oauth.net/core/1.0/#encoding_parameters > > [3] > > -http://github.com/mojodna/oauth/blob/dbd946790a882d91fb111ba64331de00... > > [4] > > -http://github.com/mojodna/oauth/blob/dbd946790a882d91fb111ba64331de00... > > > On Apr 10, 2009, at 03:47 PM, Isaac wrote: > > >> Hi, > > >> I've been using the em-dash when posting status updates, and > >> apparently this now causes the Twitter API to return "Failed to > >> validate..." errors. This just started happening within the last > >> 24-48 > >> hours. > > >> I am using OAuth (specifically, the PHP library written by Abraham > >> Williams), and my site ishttp://dora.fm. > > >> I noticed in the API changelog that accented characters -- and I'm > >> assuming, characters like the em-dash -- have supposedly been > >> "fixed" (Fixed (OAuth): Accented characters in statuses were causing > >> signature error for OAuth clients. This has been corrected.) > > >> But I'm finding that this is broken NOW and was working fine before. > > >> Suggestions? > > >> Thanks. > > > -- > > Abraham Williams |http://the.hackerconundrum.com > > Hacker |http://abrah.am|http://twitter.com/abraham > > Web608 | Community Evangelist |http://web608.org > > This email is: [ ] blogable [x] ask first [ ] private. > > Sent from Madison, Wisconsin, United States
