close
The Wayback Machine - https://web.archive.org/web/20130307231226/https://dev.twitter.com/issues/842

Issue #842: Home timeline API 1.1 returns 404 for some users.

Some of our users have reported that they are not seeing home timeline updates since we switched to the 1.1 API. We finally captured a request/response for an affected user on the https://api.twitter.com/1.1/statuses/home_timeline.json endpoint.

Note that even though the page does not exist, the rate limiting is decreased.
I don't believe this is a silly mistake on my part, as the home timeline works for most users without issues.

Thanks, @sickp

Client request:

  1. GET /1.1/statuses/home_timeline.json?count=200 HTTP/1.1
  2. Host: api.twitter.com
  3. Accept-Language: en-gb
  4. User-Agent: TweetList/3.4 iPhone5,2/6.1
  5. Accept: /
  6. X-Twitter-Client: TweetList
  7. X-Twitter-Client-Version: 3.4
  8. Connection: keep-alive
  9. X-Twitter-Client-Url: http://tweetli.st/
  10. Proxy-Connection: keep-alive
  11. Authorization: OAuth realm="", oauth_consumer_key="5Cksc2VSCduGGwQzUyiOSQ", oauth_token="17924012-jQCMjFlzMxtanWYdmIyPjDkiA2h61RE3XJsbIXwOQ", oauth_signature_method="HMAC-SHA1", oauth_signature="AJCIoj8oBsAturIEDnZo9jTtSug%3D", oauth_timestamp="1359744841", oauth_nonce="E8AD6524-AA30-416B-A657-B8242163220F", oauth_version="1.0"
  12. Cookie: lang=en; lang=en; original_referer=padhuUp37zigs9eJTisr5PnVtwPa2Ks3c0cI8B5QVqvWm4klT%2FT4%2Bv3VwLNsqsqT%2BlFFkj8BIto5KdWMNFLpHAl%2FgWpaxcQAJI87P2AU9XJlP12Yzpq%2BY600zxM3TMXC9M%2BcG%2BdjjVLrnzPQ8YRjEfLoSuhLbkKU; _twitter_sess=BAh7CToPY3JlXXXXZF9hdGwrCEQMx5E8AToMY3NyZl9pZCIlMzViOTBhMmZm%250AY2VkMjJjNjAyMmU2ZDc2NWI5Y2FiMzEiCmZsYXNoSUM6J0FjdGlvbkNvbnRy%250Ab2xsZXI6OkZsYXNoOjpGbGFzaEhhc2h7AAY6CkB1c2VkewA6B2lkIiUyZTZi%250AYTk1ZTI5MzNiZTI3YzM4MGMyODQ1OTU3ODg4MA%253D%253D--a74dedc34f78227b47115f95e20ba6768857da7f; twid=u%3D17924012%7CgTv8SWi0ERghBIU6liBqDujGw0c%3D; remember_checked=1; twll=l%3D1359655405; guest_id=v1%3A135956359063627436; k=10.35.102.122.1359563590626861
  13. Accept-Encoding: gzip, deflate

Server response:

  1. HTTP/1.1 404 Not Found
  2. Date: Fri, 01 Feb 2013 18:54:09 GMT
  3. Status: 404 Not Found
  4. Expires: Tue, 31 Mar 1981 05:00:00 GMT
  5. Pragma: no-cache
  6. X-Transaction: 7da2a12c054d60c9
  7. X-MID: 6b67beebe90e6b4dd9087f281441f59fbed0f5ef
  8. X-Frame-Options: SAMEORIGIN
  9. Last-Modified: Fri, 01 Feb 2013 18:54:09 GMT
  10. Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
  11. Set-Cookie: dnt=; domain=.twitter.com; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT
  12. Vary: Accept-Encoding
  13. X-Rate-Limit-Limit: 15
  14. X-Rate-Limit-Remaining: 14
  15. X-Rate-Limit-Reset: 1359745749
  16. Content-Type: application/json; charset=utf-8
  17. Server: tfe
  18. Content-Encoding: gzip
  19. Content-Length: 92
  20.  
  21. {"errors":[{"message":"Sorry, that page does not exist","code":34}]}

Updates

  • We're looking into resolving this issue, but you can likely mitigate it for yourself by not including cookies in your request. API v1.1 doesn't support cookies and you should omit them from you requests.