Hi Chad,
Thanks for the headers. We're working on a production issue with
slow searches right now and in the process I deployed the latest code
to the hosts and restarted. Let me know if you see any more problems.
— Matt
On Jan 29, 2009, at 11:47 AM, Chad Etzel wrote:
Just happened again... it returned the trends from about last night (i
think somewhere around 9-10PM PST). Here are the header dumps:
* About to connect() to search.twitter.com port 80 (#0)
* Trying 128.121.146.107... * connected
* Connected to search.twitter.com (128.121.146.107) port 80 (#0)
GET /trends.json?rand=9df8ebc86a49b8bb6e5f4e37b5576a7e HTTP/1.1
Host: search.twitter.com
Accept: */*
Content-Length: 7
Content-Type: application/x-www-form-urlencoded
< HTTP/1.1 200 OK
< Date: Thu, 29 Jan 2009 19:42:51 GMT
< Server: hi
< Status: 200 OK
< ETag: "51ff4c3a20fd92262dadaa468be7d198"
< Cache-Control: private, max-age=0, must-revalidate, max-age=300
< Content-Type: application/json; charset=utf-8
< X-Served-By: searchweb005.twitter.com
< Content-Length: 859
< Expires: Thu, 29 Jan 2009 19:47:51 GMT
< Vary: Accept-Encoding
< Set-Cookie:
_search_twitter_sess
=BAh7BiIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNo
%0ASGFzaHsABjoKQHVzZWR7AA%3D
%3D--105f4e06b6532a8b5e836f918bea0ef4c38e03fe;
path=/
< Connection: close
<
* Closing connection #0
-1 - 1 - #Lost
-1 - 2 - Obama
-1 - 3 - Melbourne
-1 - 4 - Top Chef
-1 - 5 - Slumdog Millionaire
-1 - 6 - Goodnight
-1 - 7 - Lie To Me
-1 - 8 - iTunes
-1 - 9 - Charles Widmore
-1 - 10 - Mars
-Chad
On Thu, Jan 29, 2009 at 1:03 PM, Matt Sanford <[email protected]>
wrote:
Hi Chad,
I haven't seen anything like that. If you are still seeing it can
you try
using 'curl -v' or capturing the headers in your application? It
will help
me find out what server might be causing problems.
Thanks;
— Matt
On Jan 29, 2009, at 10:00 AM, Chad Etzel wrote:
Hi there,
I am seeing some strange behavior that the trends.json info is
intermittently being returned with old data (e.g. from last
night). I
don't think it's a local machine caching issue, since I saw the same
old data returned on two separate machines at the same time. Is
anyone else experiencing this? I have tried appending a random
value
on the end of the request (i.e. trends.json?rand=983yq928ry923y9qu )
to force avoiding caching issues...
Thanks,
-Chad
