[twitter-dev] Re: non json response
I just had one non-json response, in the middle of about 10 requests
made with curl -vvv (other responses were correct)
Below are 3 requests and the non-json response bracketted by 2 good
responses which contain the response time and other logging data.
HTH
Rudi
rudolf-farkass-macbook-pro:TwitterWeb rudifarkas$ curl -vvv
http://twitter.com/users/show/rudifa.json
* About to connect() to twitter.com port 80 (#0)
* Trying 168.143.161.20... connected
* Connected to twitter.com (168.143.161.20) port 80 (#0)
> GET /users/show/rudifa.json HTTP/1.1
> User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3
> OpenSSL/0.9.7l zlib/1.2.3
> Host: twitter.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Sun, 13 Sep 2009 09:45:23 GMT
< Server: hi
< X-RateLimit-Limit: 150
< X-Transaction: 1252835123-2408-31139
< Status: 200 OK
< ETag: "df090f6c8147e20ba7fe81315a66b9af"
< Last-Modified: Sun, 13 Sep 2009 09:45:23 GMT
< X-RateLimit-Remaining: 124
< Content-Type: application/json; charset=utf-8
< Pragma: no-cache
< Content-Length: 1176
< Cache-Control: no-cache, no-store, must-revalidate, pre-check=0,
post-check=0
< Expires: Tue, 31 Mar 1981 05:00:00 GMT
< X-Revision: a62881015b2c2fb6f795bf931bd56bd494f37254
< X-RateLimit-Reset: 1252836853
< Set-Cookie: lang=en; path=/
< Set-Cookie:
_twitter_sess=BAh7CDoRdHJhbnNfcHJvbXB0MDoHaWQiJWU5OGQyZmU3NWVkY2RhZjhkYTk5%250ANTBlNTA4OTk0MzhhIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFz
%250AaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--66931156c75554797fc576876bdec52dc705736e;
domain=.twitter.com; path=/
< Vary: Accept-Encoding
< Connection: close
<
* Closing connection #0
{"profile_sidebar_border_color":"BDDCAD","description":"Wrote firmware
for world-class osciloscopes for many years. Now learning iPhone
programming tricks. Loves
skiing.","url":null,"screen_name":"rudifa","status":
{"in_reply_to_status_id":null,"favorited":false,"in_reply_to_user_id":null,"source":"http://apiwiki.twitter.com/\"; rel=\"nofollow\">API","created_at":"Thu Sep 10 16:49:49 +
2009","in_reply_to_screen_name":null,"id":
3890997267,"truncated":false,"text":"De retour de la T\u00eate de
Parmelan"},"following":null,"verified":false,"profile_text_color":"33","followers_count":
9,"profile_background_image_url":"http://a1.twimg.com/
profile_background_images/17762518/
DSC01211-63-2.jpeg","created_at":"Thu Apr 30 22:42:35 +
2009","notifications":null,"friends_count":
29,"profile_link_color":"0084B4","profile_background_tile":false,"favourites_count":
0,"profile_background_color":"9AE4E8","protected":false,"time_zone":"Bern","location":"Geneva","name":"Rudi
Farkas","profile_sidebar_fill_color":"DDFFCC","id":
36797542,"statuses_count":52,"utc_offset":
3600,"profile_image_url":"http://a1.twimg.com/profile_images/311858510/
me-bsp-6a_normal.png"}
rudolf-farkass-macbook-pro:TwitterWeb rudifarkas$ curl -vvv
http://twitter.com/users/show/rudifa.json
* About to connect() to twitter.com port 80 (#0)
* Trying 168.143.161.20... connected
* Connected to twitter.com (168.143.161.20) port 80 (#0)
> GET /users/show/rudifa.json HTTP/1.1
> User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3
> OpenSSL/0.9.7l zlib/1.2.3
> Host: twitter.com
> Accept: */*
>
< HTTP/1.0 200 OK
< Connection: Close
< Pragma: no-cache
< cache-control: no-cache
< Refresh: 0.1
< Content-Type: text/html; charset=iso-8859-1
<
http://www.w3.org/
TR/1999/REC-html401-19991224/strict.dtd">
* Closing connection #0
rudolf-farkass-macbook-pro:TwitterWeb rudifarkas$ curl -vvv
http://twitter.com/users/show/rudifa.json
* About to connect() to twitter.com port 80 (#0)
* Trying 168.143.161.20... connected
* Connected to twitter.com (168.143.161.20) port 80 (#0)
> GET /users/show/rudifa.json HTTP/1.1
> User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3
> OpenSSL/0.9.7l zlib/1.2.3
> Host: twitter.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Sun, 13 Sep 2009 09:45:35 GMT
< Server: hi
< X-RateLimit-Limit: 150
< X-Transaction: 1252835135-57410-29384
< Status: 200 OK
< ETag: "df090f6c8147e20ba7fe81315a66b9af"
< Last-Modified: Sun, 13 Sep 2009 09:45:35 GMT
< X-RateLimit-Remaining: 123
< Content-Type: application/json; charset=utf-8
< Pragma: no-cache
< Content-Length: 1176
< Cache-Control: no-cache, no-sto
[twitter-dev] Re: non json response
I have seen this same http page with empty body http://www.w3.org/ TR/1999/REC-html401-19991224/strict.dtd"> a number of times in the last few days (but intermittently - a good response may come after several attempts), in response to http://twitter.com/users/show/rudifa.json The most recent one was on UTC time 2009-09-06 18:55:38.262 My IP is 84.227.186.88 as reported by http://www.whatismyip.com/ Could someone at twitter.com please tell us what does this mean? Server (s) overloaded? On Aug 30, 1:20 pm, Steven Wilkin wrote: > I'm consistently getting the same response when > accessinghttp://search.twitter.com/trends.jsonfrom 209.40.204.183 > > Steve > > On Aug 26, 5:27 pm, Ryan Sarver wrote: > > > Ben, > > > It's a known issue and we are trying to hunt it down. Can you please > > provide us with your source IP and an approximate time of when you saw > > it? > > > Thanks, RyanOn Wed, Aug 26, 2009 at 7:00 AM, > > ben wrote: > > > > Occassionally i get back a 200 status html response from the json > > > search api which look like this, most times the same search works > > > fine, it just happens occassionally: > > > > http://www.w3.org/ > > > TR/1999/REC-html401-19991224/strict.dtd"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Does anyone recognise what this kind of response means? Is it normal, > > > or just beta-ish quirks?
[twitter-dev] Re: Followers & Friends IDs Are Seriously MESSED Up!
Hello I am seeing right now (14:45 UTC) discrepancy between the list of my followers as reported by my home page at Twitter.com (which is correct) and the list reported by the API - which seems to be several days old (it includes several followers that I blocked recently). Is anyone else seeing this? On Sep 5, 4:09 pm, Dewald Pretorius wrote: > Awesome. Thanks John, and also to everyone who made this happen. > > Dewald > > On Sep 5, 10:55 am, John Kalucki wrote: > > > Thanks to the efforts of many working late into a Friday night, we > > deployed a fix for this issue starting at about 11pm PDT. The fix was > > verified as working in production at about 12:05am PDT. > > > -John Kaluckihttp://twitter.com/jkalucki > > Services, Twitter Inc. > > > On Sep 5, 5:36 am, Dewald Pretorius wrote: > > > > John, > > > > Just so we know, is this 5,000 thing going to be fixed over the > > > weekend, or will we have to wait until Tuesday? > > > > Dewald > > > > On Sep 5, 12:35 am, John Kalucki wrote: > > > > > We're aware of the problem with the following API not returning more > > > > than 5,000 followers. Apparently this call has recently been > > > > unreliable was often timing out and returning 503s. A change to fix > > > > the 503s limited the results to 5000 followers prematurely. We're > > > > going to get this back to the >5000 followers, but with 503's state as > > > > soon as we can, but we're fighting several fires at once tonight. > > > > > More in a few minutes. > > > > > -John > > > > > On Sep 4, 7:56 pm, Dewald Pretorius wrote: > > > > > > Not only do the social graph calls now suddenly, without any prior > > > > > warning of announcement, return only 5,000 ids, it is messed up even > > > > > when you do the paging as per the API documentation. > > > > > > Case in point. @socialoomph has 16,598 followers. If you page through > > > > > the follower ids with &page, you get only 12,017 entries. > > > > > > This is highly frustrating, and it has now completely screwed up my > > > > > follower processing. It does not help that Twitter has rolled out > > > > > something into production without any kind of testing, right before a > > > > > weekend. > > > > > > Dewald
[twitter-dev] Re: change my image ; old profile_image_url seen in response to users/show
Thank you, Clint After I posted my questions I went out for a long walk. Now, almost 90 min later, both queries (curl http://twitter.com/users/show/rudifa.json and curl http://twitter.com/users/show/rudifa.xml) do return the updated image url. Rudi
[twitter-dev] change my image ; old profile_image_url seen in response to users/show
Hello all Today I changed my profile image (several times) via twitter web page, Settings - Picture The changed picture appeared immediately in the web pages (That's a nice picture ...), and the new url can be seen with the browser's Copy Image Location : http://s3.amazonaws.com/twitter_production/profile_images/311858510/me-bsp-6a_normal.png However, subsequent users/show queries (from curl or from browser address bar) return responses that contain old urls - not the same one either : curl http://twitter.com/users/show/rudifa.json http://s3.amazonaws.com/twitter_production/profile_images/198907870/Snapshot_of_me_1_normal.png curl http://twitter.com/users/show/rudifa.xml http://s3.amazonaws.com/twitter_production/profile_images/311647072/Snapshot_of_me_1_normal.png Is this a known problem ? Does the twitter server perform some kind of caching that would explain this ? Any ideas for getting immediately an up-to-date response from twitter server would be appreciated. Rudi
