home_timeline.json return error 404 (page not found) if used through secure connection (https)?


#1

HI,

I 'm developing a client for windows 8; I noticed one strange behavior

when retrieving
https://api.twitter.com/1.1/statuses/home_timeline.json

I always get 404 erorr (tried with 3 different accounts)

reverting to v 1 of the api solves the problem; also using insecure connection (http://api.twitter.com/1.1/statuses/home_timeline.json) works fine…

Note that this is only happening with home_timeline other endpoints works as expected…

=== BEGIN REQUEST ====

GET https://api.twitter.com/1.1/statuses/home_timeline.json?contributor_details=true&count=100&exclude_replies=false&include_entities=true&trim_user=false HTTP/1.1
Authorization: OAuth oauth_consumer_key=“XXXXXX”, oauth_nonce=“Ja4S5rX5bOQj”, oauth_signature=“dRhMS4zuzu9BpuT%2BN%2FT4ca2M7Vo%3D”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1352705412”, oauth_token=“XXXXXX”, oauth_version="1.0"
Host: api.twitter.com
Cookie: lang=en; k=10.35.41.121.1352705353793854; guest_id=v1%3A135270535379633751; twid=u%3D21224692%7CQ9vhbWOjLiEZdbyzw0LwZb7GkXc%3D; _twitter_sess=BAh7CToMY3NyZl9pZCIlNGM1NjFiMThhNmVkMTAyYWYyZGEwM2M1ZWZhYjlh%250ANDk6D2NyZWF0ZWRfYXRsKwhOqIXzOgE6B2lkIiU0YjRjYTAzNTYwZDc1YzMw%250ANTUyZTQ1NDhjOTJkOWI1MSIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6%250ARmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA%253D%253D–c561cd585205bfbbbbf3833dabe6984105d5583e

=== END REQUEST ====

=== BEGIN RESPONSE ====

HTTP/1.1 404 Not Found
Date: Mon, 12 Nov 2012 07:30:14 GMT
Status: 404 Not Found
X-Frame-Options: SAMEORIGIN
Expires: Tue, 31 Mar 1981 05:00:00 GMT
X-Transaction: 45f6f971d423d168
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
Last-Modified: Mon, 12 Nov 2012 07:30:14 GMT
X-MID: d367c1804097a2edeeea0756c82ff03e52bf6bec
Pragma: no-cache
Set-Cookie: dnt=; domain=.twitter.com; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: _twitter_sess=BAh7CToMY3NyZl9pZCIlNGM1NjFiMThhNmVkMTAyYWYyZGEwM2M1ZWZhYjlh%250ANDkiCmZsYXNoSUM6J0FjdGlvbkNvbnRyb2xsZXI6OkZsYXNoOjpGbGFzaEhh%250Ac2h7AAY6CkB1c2VkewA6D2NyZWF0ZWRfYXRsKwhOqIXzOgE6B2lkIiU0YjRj%250AYTAzNTYwZDc1YzMwNTUyZTQ1NDhjOTJkOWI1MQ%253D%253D–4853d25d45577729b8af64653429ab249d907d9b; domain=.twitter.com; path=/; HttpOnly
Vary: Accept-Encoding
X-Rate-Limit-Limit: 15
X-Rate-Limit-Remaining: 11
X-Rate-Limit-Reset: 1352706096
Content-Type: application/json; charset=utf-8
Content-Length: 68
Server: tfe

{“errors”:[{“message”:“Sorry, that page does not exist”,“code”:34}]}

=== END RESPONSE ====

Thanks


#2

I’ve been looking into reports of this that I cannot reproduce.

Are you intentionally sending a cookie along with your request? What happens if you omit the cookie? Is this your personal account that this is occurring with?


#3

HI

Yes its my personal account (but I also tried some test accounts)

I’m not sending any cookies (intentionally)…

Know what I have modified my code to eliminate sending cookies and it WORKED!!

Thanks for the hint…


#4

Glad this seemed to have fixed this for you.