Request address was http://api.twitter.com/1/statuses/home_timeline.json?count=200&since_id=18937297074
Don't know how to get the rest.

Response=

Date: Mon, 19 Jul 2010 19:34:27 GMT
Server: hi
Status: 200 OK
X-Transaction: 1279568067-371-18115
X-Transaction: 1279568067-371-18115
X-RateLimit-Limit: 150
X-RateLimit-Limit: 150
ETag: "436458580446ee43d8d16a7f59188e7e"
ETag: "436458580446ee43d8d16a7f59188e7e"
Last-Modified: Mon, 19 Jul 2010 19:34:27 GMT
Last-Modified: Mon, 19 Jul 2010 19:34:27 GMT
X-RateLimit-Remaining: 143
X-RateLimit-Remaining: 143
X-Runtime: 0.05456
X-Runtime: 0.05456
Content-Type: text/html; charset=utf-8
Content-Length: 46998
Content-Length: 4659
Pragma: no-cache
Pragma: no-cache
X-RateLimit-Class: api
X-RateLimit-Class: api
X-Revision: DEV
X-Revision: DEV
Expires: Tue, 31 Mar 1981 05:00:00 GMT
Expires: Tue, 31 Mar 1981 05:00:00 GMT
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
X-RateLimit-Reset: 1279570023
X-RateLimit-Reset: 1279570023
Set-Cookie: k=67.176.217.52.1279568067505660; path=/; expires=Mon, 26-Jul-10 19:34:27 GMT; domain=.twitter.com Set-Cookie: guest_id=12795680675365717; path=/; expires=Wed, 18 Aug 2010 19:34:27 GMT
Set-Cookie: lang=en; path=/
Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCOY7M%252BwpAToHaWQiJWIxNjMxMmM2OWE0Yzg4%250AYzZiYzNkYjczY2IzOWE5NjQyIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--9760890cd67ae21e1415b4f4fd5f04f4a1a4e876; domain=.twitter.com; path=/
Vary: Accept-Encoding
Connection: close


On 07/19/2010 02:53 PM, Taylor Singletary wrote:
Hi Everyone,

This sounds very strange. Anyone have any captures of the entire request sequence? - Your HTTP headers, including acceptance headers, the full URI being executed, etc.
  - The full response, including HTTP Headers

(as can be provided without compromising private user / app data)

Thanks!
Taylor


On Mon, Jul 19, 2010 at 12:36 PM, Bill Jacobson <gabe...@gmail.com <mailto:gabe...@gmail.com>> wrote:

    I'm expecting 'application/json' and am suddenly getting 'text/html'.


    On 07/19/2010 01:58 PM, Rich wrote:

        I'm seeing an increase in the home timeline returning a
        content-type
        of text/html instead of text/xml

        The actual body of the request is actually the correct XML
        response
        but my app checks for the correct HTTP header content-type.

        Is anyone else seeing this?



Reply via email to