Andrew, Thanks for bumping this up to us. Can you please also provide some additional data to us (as much as you can) so we can help figure out what is going on and where it is coming from?
1. The IP of the machine making requests to the Twitter API. If you're behind NAT, please be sure to send us your *external* IP. 2. The IP address of the machine you're contacting in the Twitter cluster. You can find this on UNIX machines via the "host" or "nslookup" commands, and on Windows machines via the "nslookup" command. 3. The Twitter API URL (method) you're requesting and any other details about the request (GET vs. POST, parameters, headers, etc.). 4. Your host operating system, browser (including version), relevant cookies, and any other pertinent information about your environment. 5. What kind of network connection you have and from which provider, and what kind of network connectivity devices you're using. Thanks in advance. Best, Ryan On Tue, Aug 18, 2009 at 7:37 AM, Andrew<andrewcuri...@gmail.com> wrote: > > I get this response quite frequently: > > <!-- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" > "http://www.w3.org/TR/html4/strict.dtd";> --> > <HTML> > <HEAD> > <META HTTP-EQUIV="Refresh" CONTENT="0.1"> > <META HTTP-EQUIV="Pragma" CONTENT="no-cache"> > <META HTTP-EQUIV="Expires" CONTENT="-1"> > <TITLE></TITLE> > </HEAD> > <BODY><P></BODY> > </HTML> > > And other people are getting it as well ( > http://groups.google.com/group/twitter-development-talk/browse_thread/thread/acdcb4baf76037c8/e0ac9745e4c9bfe9?lnk=gst&q=refresh#e0ac9745e4c9bfe9 > ). > > What is the recommended way of handling this? I could do an immediate > refresh and hope for the best, which is my initial thought. But the > other question is, why is a request for JSON returning HTML? > > The request that seems to be the most problematic for me in this > regard is: > http://twitter.com/statuses/friends.json > > I am authenticating via OAuth and not using Curl. >
