Not lately but on Sept 9 I see this in our logs. URL http://twitter.com/account/verify_credentials.json
HEADERS Expect: Authorization: OAuth realm="http://twitter.com/account/ verify_credentials.json",oauth_consumer_key="[snip]",oauth_token="[snip]",oauth_nonce="15581955d5d3cd6ef94193cf853745fc",oauth_timestamp="1252539951",oauth_signature_method="HMAC- SHA1",oauth_version="1.0",oauth_signature="[snip]" User-Agent: EpiTwitter (http://github.com/jmathai/twitter-async/tree/) RESPONSE CODE 200 RESPONSE BODY <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/ TR/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> On Sep 17, 9:26 pm, Chad Etzel <c...@twitter.com> wrote: > Hi all, > > We've had a few sporadic reports lately that the data returned from > the api appears to be garbled. This is separate from the 200 HTML > errors and 408's of late; this is actual malformed XML or JSON data. > > If you are seeing this, can you please specify: > > Are you using the REST or Streaming API? > > XML or JSON? > > What is the exact URL you are using to request the data? > > What username are you using to connect (if applicable)? > > Feel free to unicast me the information. > > Thanks, > -Chad
