As stated in Ryan's email, you should respect 302 responses. In curl this can be accomplished with the --location flag. See the man page for more details.
-Chad On Fri, Aug 7, 2009 at 3:10 PM, Chris<kiraili...@gmail.com> wrote: > > Thank you for updating us! > > I have still a problem with getting search results via curl like > described here: http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search > This was working pretty good before the DDoS attack, but now I don't > get any results just http_code of 302. > > An example url, I'm trying to get is: > http://search.twitter.com/search.atom?q=twitter&lang=de&rpp=15&since_id=3170060360&show_user=true > > Can you give me a hint what I'm doing wrong or is this part of the API > still not working correct? > > > Thanks and best regards, > Chris >