Ah. Our new support site may have clobbered this URL. Please file an issue here: http://code.google.com/p/twitter-api/issues/entry.
On Fri, Jan 16, 2009 at 15:45, Eric Blair <[email protected]> wrote: > > I'm getting a 301 error when I call the test method. I was using test > as a check to see if Twitter was up before doing the bulk of my calls, > so this threw my scripts for a bit of a loop. > > http://twitter.com/help/test.xml > > returns > HTTP/1.1 301 Moved Permanently > Date: Fri, 16 Jan 2009 23:44:50 GMT > Server: Apache > Location: http://help.twitter.com/ > Cache-Control: max-age=300 > Expires: Fri, 16 Jan 2009 23:49:50 GMT > Vary: Accept-Encoding > Content-Length: 232 > Connection: close > Content-Type: text/html; charset=iso-8859-1 > > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>301 Moved Permanently</title> > </head><body> > <h1>Moved Permanently</h1> > <p>The document has moved <a href="http://help.twitter.com/";>here</ > a>.</p> > </body></html> > > --Eric > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
