The Wayback Machine - https://web.archive.org/web/20121214192049/https://dev.twitter.com/issues/712

Issue #712: gzipped response for DM's

Hello,

For the past few days we are receiving gzipped response for the api "http://api.twitter.com/1/direct_messages.xml" even though we have explicitly specified otherwise. Below is the sample of the header recieved

User-Agent: Mozilla/4.0
Accept: application/xml
Connection: close
Content-Type: application/xml; charset=utf-8
Authorization: OAuth oauth_consumer_key="ABCD", oauth_nonce="...", oauth_signature_method="HMAC-SHA1", oauth_signature="XXXXX", oauth_timestamp="1354602729", oauth_token="XXXXXXX", oauth_version="1.0"
Cookie: ...

EAITransport EAITransportDebug 4 0000000250bd201c:0 2012-12-04 09:32:09 *** HTTP response Headers from Data Send request:
HTTP/1.1 200 OK
Date: Tue, 04 Dec 2012 06:31:58 GMT
Status: 200 OK
Pragma: no-cache
X-Frame-Options: SAMEORIGIN
X-RateLimit-Limit: 350
X-MID: a6be4c145dcae36cc9bac0a2ad8c72c31a71ad78
X-Transaction: e90dcbc3b2899a96
X-Transaction-Mask: a6183ffa5f8ca943ff1b53b5644ef114b28557d5
X-RateLimit-Reset: 1354606271
ETag: "e3ca0f5421ce0878dd9fefb7edcc91d1"
X-Access-Level: read-write-directmessages
X-RateLimit-Class: api_identified
X-RateLimit-Remaining: 348
X-Runtime: 0.03964
Last-Modified: Tue, 04 Dec 2012 06:31:57 GMT
Content-Type: application/xml; charset=utf-8
Expires: Tue, 31 Mar 1981 05:00:00 GMT
Vary: Accept-Encoding
Server: tfe
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0, proxy-revalidate
Content-Length: 2808
Connection: close
Content-Encoding: gzip
Set-Cookie: dnt=; domain=.twitter.com; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT

Updates

  • Appears to be related to the user agent. Removing that header should return a non-gzipped response until we're able to deploy a fix.