Hi Chad,
We were rolling out a new cache layer to guard against some abuse
cases and this might have been during the roll out. Are you still
seeing the <esi:include> stuff? If so please let me know and we'll
turn irt off. If not then you can expect less search rate limiting and
improved response times in the near future.
Thanks;
— Matt Sanford
On Feb 5, 2009, at 11:49 AM, Chad Etzel wrote:
I have been making my usual search.json requests w/ my apps today, and
all the sudden I am seeing these types of responses:
Request URL:
http://search.twitter.com/search.json?callback=search_func2&q=jazzychad&rpp=20&since_id=1180576890&rand=5736910
Response:
callback_func(<esi:include
src="/search.json?q=jazzychad&rpp=20&since_id=1180576890"/>);
Anyone else seeing this?
Here are the headers... apologies for FireBug semi-mangling the
output.
Response Headers
Date
Thu, 05 Feb 2009 19:19:27 GMT
Server
hi
Status
200 OK
Etag
"b297b89210de5dd868c6dcd14d2df418"-gzip
Cache-Control
max-age=20, must-revalidate, max-age=300
Content-Type
application/json; charset=utf-8
X-Served-By
searchweb005.twitter.com
Expires
Thu, 05 Feb 2009 19:24:27 GMT
Content-Encoding
gzip
Content-Length
109
Vary
Accept-Encoding
X-Varnish
1220807190
Age
0
Via
1.1 varnish
X-Cache-Svr
searchweb005.twitter.com
X-Cache
MISS
Connection
close
Request Headers
Host
search.twitter.com
User-Agent
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080207
Ubuntu/7.10 (gutsy) Firefox/2.0.0
.12
Accept
*/*
Accept-Language
en-us,en;q=0.5
Accept-Encoding
gzip,deflate
Accept-Charset
ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive
300
Connection
keep-alive
Referer
http://tweetgrid.com/grid?l=2
