This happens to me when I do json get requests as well. It happens very inconsistently during a normal session, but I can almost always reproduce it if I let the client sit for a while and then try.
Is almost as if the server can't authenticate the request fast enough and throws back an empty html page by default. On Sep 7, 10:48 am, Rich <[email protected]> wrote: > Can we please hear something from someone at Twitter about this, it's > becoming unusable with constant XML errors > > On Sep 7, 4:51 am, Naveen A <[email protected]> wrote: > > > We are seeing this HTML META REFRESH as well from our clients. We are > > a mobile application and seeing this issue more and more frequently to > > the point that application is not functioning properly, its hard for > > use to provide any specific ip data as the carriers are most likely > > proxying the requests from the device. > > > It is not limited to a specific api call either, it is a systemic > > issue across a wide range of calls we make. > > > There was a ticket related to the issue in the bug tracker for search, > > but it has been closed and I think it should be re-opened as it is > > still a problemhttp://code.google.com/p/twitter-api/issues/detail?id=968 > > > Any feedback would be appreciated. > > > On Sep 6, 3:01 pm, Rich <[email protected]> wrote: > > > > Yeah it's happening to me again, same as my previous email, except the > > > time stamp will be around 2 minutes ago > > > > On Sep 6, 4:05 pm, twittme_mobi <[email protected]> wrote: > > > > > Hi Ryan, > > > > > I am getting the same error - i can found it in the logs of my app > > > > every day - at least 20 times. > > > > > 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. > > > > > ---> > > > > Name: twittme.mobi > > > > Address: 67.222.129.154 > > > > > 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. > > > > > ---> > > > > Name: twitter.com > > > > Address: 128.121.146.100 > > > > > 3. The Twitter API URL (method) you're requesting and any other > > > > details about the request (GET vs. POST, parameters, headers, etc.). > > > > > ---> > > > > 'account/rate_limit_status.xml' > > > > > 4. Your host operating system, browser (including version), relevant > > > > cookies, and any other pertinent information about your environment. > > > > > ---> > > > > Linux, mobile browser,firefox, no cookies used. > > > > > 5. What kind of network connection you have and from which provider, > > > > and what kind of network connectivity devices you're using. > > > > > ---> > > > > devices are mostly mobile..probably using mobile connections or > > > > wireless. > > > > > Thanks! > > > > > On Sep 5, 2:54 pm, Alex <[email protected]> wrote: > > > > > > hi Ryan, > > > > > any update on this issue ? > >
