I’m still seeing this too. I will re-iterate that the vast majority of the API calls return with correct header, but I’m still consistently seeing problem responses frequently.
As @markunsworth pointed out above, I’ve now also detected errors in other headers. Here are some snippets of problem headers that came in overnight:
content-encoding: gzip
content-encoding: macaw_search
content-length: 67529
content-length: api.twitter.com
content-disposition: api.twitter.com
content-encoding: 00644bdb0068deb5
content-length: 43
content-length: 37
content-length: 46093
content-type: text/html; charset=ISO-8859-1
content-encoding: macaw_search
content-length: 59076
content-length: api.twitter.com
It is also really surprising that one of the header sets above included “charset=ISO-8859-1”, as my understanding is that the twitter api “always” returned utf-8 data?
I do get notified by my s/w whenever an unparseable response is returned from a Twitter API call and in the past that happened, maybe, once every couple of months or so - so infrequently that I never bothered to look into it. That changed abruptly at 5:30pm Eastern Time on Nov 7 and since then these errors have been occurring frequently.
I’ve been capturing the “full response - including headers” (like the one I pasted into the first post on this thread) for unparsable responses on a couple of my servers since about 10am ET yesterday (Nov 8). @andypiper if you want me to package these up and send them along, just ask.
