In my testing, I got the 401 error when posting a simple status such as "testing testing" instead of normalizing it to "testing%20testing". I can't tell if it's the "invalid signature" error since I can't figure out how to see that in .Net, but I can see that it's the "401: Unauthorized" error.
Ryan On Thu, Feb 18, 2010 at 3:03 PM, Dewald Pretorius <dpr...@gmail.com> wrote: > Ryan, > > Is that with just plain ASCII in the update text that you get a 401 > when not normalized? > > The bulk of my signatures work fine, and I'm not normalizing at this > point. It's just now and again that Twitter says 401 Invalid signature > on a status update. So, I wondering if the text has some strange > characters that cause a discrepancy between my sig calc and their sig > check. > > On Feb 18, 3:13 pm, Ryan Alford <ryanalford...@gmail.com> wrote: > > I just tried it and I do get the 401 Unauthorized error when I don't > > normalize the status text. > > > > Ryan > > > > On Thu, Feb 18, 2010 at 1:07 PM, Dewald Pretorius <dpr...@gmail.com> > wrote: > > > Can computing the OAuth signature on un-normalized tweet text cause > > > Incorrect Signature issues? >
