I may be the only one to be this stupid, but when I looked at my POST
request functions, I was appending some parameters like "Source", etc.
that were common to all requests. But since they weren't there when
the signature was generated, we were getting 401 errors as of 7/27.
Removing those fixed us right up.
On Jul 28, 12:46 am, Duane Roelands <duane.roela...@gmail.com> wrote:
> From my experimenting, it appears that posting a tweet is successful
> if the text contains no spaces. Once you have a space in the tweet,
> it fails. Researching...
> On Jul 28, 12:29 am, winrich <winric...@gmail.com> wrote:
> > ok guys.
> > so my calls were failing on the verify_credentials call and not on the
> > update or timeline calls. the only difference i saw was the the
> > verify_credential call wasn't secured. i changed it to https and it
> > worked. ??? lol
> > On Jul 27, 9:19 pm, Chad Etzel <jazzyc...@gmail.com> wrote:
> > > On Mon, Jul 27, 2009 at 11:55 PM, Duane
> > > Roelands<duane.roela...@gmail.com> wrote:
> > > > RTFM is not a helpful answer, especially when many developers are
> > > > relying on libraries that they did not write.
> > > That's a risk you run when using code you didn't write.
> > > I'm not saying that this situation doesn't suck for those affected.
> > > I'm sure that it does. But, for a technology so new as OAuth, the
> > > libraries may not be mature yet.
> > > Officially, Twitter OAuth is still in Public Beta and has never been
> > > officially recommended to integrate into production code. That being
> > > said, there could still be a problem on Twitter's end with their
> > > signature verification mechanism and the libraries could all be valid.
> > > I don't have a way of knowing.
> > > I do agree that at least a note that "a security change was pushed
> > > today" would be nice, though.
> > > -Chad