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

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?

Reply via email to