Thank you both.
On Sep 8, 1:47 pm, Naveen A <knig...@gmail.com> wrote: > While this issue is known and does show up on the list fairly > frequently, I think the best solution is to point users who report > this to the number of existing issues filed for this bug so that they > may STAR them and be kept up to date about what is going on with the > issue. > > http://code.google.com/p/twitter-api/issues/detail?id=1014http://code.google.com/p/twitter-api/issues/detail?id=1015http://code.google.com/p/twitter-api/issues/detail?id=968 > > On Sep 8, 12:02 pm, JDG <ghil...@gmail.com> wrote: > > > > > This is a very known issue and there are threads about it in this group once > > every 18 or so hours. > > > On Tue, Sep 8, 2009 at 09:38, Francis Shanahan > > <francisshana...@gmail.com>wrote: > > > > I'm calling :http://twitter.com/users/show.xml > > > > My request works fine, it's signed correctly with a valid token etc. > > > > Every so often I get this response: > > > > <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/ > > > TR/1999/REC-html401-19991224/strict.dtd<http://www.w3.org/%0ATR/1999/REC-html401-19991224/strict.dtd>"> > > > <!-- <!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> > > > > No error is thrown and no reason code or anything comes back. > > > > Is this a bug on the Twitter side? Is this a known issue? > > > > -fs > > >http://tweetarun.com > > > -- > > Internets. Serious business.
