I am getting 404 just for search api, it was working just fine all along. I get 404 on production server but works fine on dev and qa boxes - not sure why. My assumption is our production server was active during DDos attack and has been blacklisted. Am I right? how can I whitelist/fix it?
On Aug 7, 12:22 pm, Simon Tiplady <[email protected]> wrote: > Chris, > > A 302 header means you need to request the location that twitter has > sent back to you with that header. > It is part of their attempts at spotting the real requests from the > fake ones. > How you handle it all depends on what language you are programming in! > > Simon > > On Aug 7, 8:10 pm, Chris <[email protected]> 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〈=de&rpp=15&since_... > > > 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
