- here notification about dropping cursorless getting.

Twitter returns ETag header in HTTP response. I'm getting something
like this:

bob...@callisto ~ % curl -X HEAD -I "
HTTP/1.1 200 OK
Date: Fri, 08 Jan 2010 02:37:58 GMT
Server: hi
X-RateLimit-Limit: 150
X-Transaction: 1262918279-26464-30450
Status: 200 OK
ETag: "cfaf04c2b90a7999ac0d25df7ef061fd"
Last-Modified: Fri, 08 Jan 2010 02:37:59 GMT
X-RateLimit-Remaining: 94
X-Runtime: 0.02614
Content-Type: application/json; charset=utf-8
Pragma: no-cache
Content-Length: 6662
X-RateLimit-Class: api
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-
Expires: Tue, 31 Mar 1981 05:00:00 GMT
X-Revision: DEV
X-RateLimit-Reset: 1262920599
%250AaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--528b531f0593cdc9b05c4ffffeaa1a976e1ce2d2;; path=/
Vary: Accept-Encoding
Connection: close

Is ETag always refers to exactly one followers state? E.g. if someone
added/removed from that list, checksum strictly will be different?

Why doesn't twitter API wiki describe HEAD requests? May be so useful
if developers can trust them, of course.

Reply via email to