Hmm, Unfortunately this 302 business will completely goof OAuth calls.
If you are able to programmatically see that you are getting these redirects, try calling the account/rate_limit_status call  (it could be any call, but this one is "free" and is a GET). You should still get a 302 (I'm pretty sure). Then if you jump through the redirect hoops with this call, it should clear you from more 302's for a while. I'm out today, but if someone could try this and report back if it works that would be helpful.  http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0rate_limit_status Thanks, -Chad On Sat, Aug 8, 2009 at 6:31 AM, timwhitlock<tim.whitl...@publicreative.com> wrote: > > I've seem the 302 Location headers having invalid URLs... i.e. two "?" > symbols. > The original query string and then an additional "?" for the token at > the end. > Following this redirect blindly has resulted in a Forbidden response. > > Also it is unclear whether the redirect location needs to be re- > signed? (I am not doing so, but may explain the 403?) > > > > > > On Aug 8, 8:14 am, Rich <rhyl...@gmail.com> wrote: >> Excellent our client now supports the 302's :) >> >> On Aug 8, 7:37 am, Chad Etzel <c...@twitter.com> wrote: >> >> > You may have to follow redirects more than once *wink wink nudge nudge* >> >> > with curl you can add --location flag. There's a good bit of info in >> > the man page as well. >> >> > If using curl with PHP, you can set: >> > curl_setopt($ch, CURLOPT_FOLLOWLOCATION, TRUE); >> >> > HTH, >> > -Chad >> >> > On Sat, Aug 8, 2009 at 1:31 AM, TjL<luo...@gmail.com> wrote: >> >> > > All of my scripts check for "Status 200" before proceeding. >> >> > > Now we are (sometimes) getting a 302, but when I try >> >> > > curl --netrc -s -D -http://twitter.com/account/rate_limit_status.xml >> >> > > Gave me a 302 with a Location of: >> >> > >http://twitter.com/account/rate_limit_status.xml?c73f7db0 >> >> > > but when I tried >> >> > > curl --netrc -s -D - >> > > 'http://twitter.com/account/rate_limit_status.xml?c73f7db0' >> >> > > it seemed to want to redirect me to >> >> > >http://twitter.com/account/rate_limit_status.xml >> >> > > If "accepting 30x" is a requirement now, I'd like some advice on how to >> > > do so. >> >> > > TjL >