On Thu, Aug 6, 2009 at 3:10 PM,
timwhitlock<tim.whitl...@publicreative.com> wrote:
> I'm getting the same thing.
> I patched my library to follow the redirect, but that just results in
> a 403.
> The addition of the mysterious token actually creates an invalid URL,
> because it ends up with two "?"s
> I have two api keys for my app. One for my local dev server, and a
> different one for deploying to live.
> My dev calls work fine. the problem only occurs on the live server. My
> live server IP is whitelisted, so I don't know if that's relevant.

I don't think it is relevant because the addresses my queries are
coming from are not whitelisted.

I'm also still seeing this behavior this morning. It'd be nice just to
know that someone at Twitter knows why this is happening and is going
to get it fixed at some point.

Anthony Eden

GMU/IT d- s: a32 C++(++++)$ UL@ P--- L+(++) !E W+++$ !N o? K? w--- !O
M++ V PS+ PE Y PGP t+ !5 X- R tv b++ DI+ D++ G- e++ h---- r+++ y++++**


Reply via email to