Hello Twitter dev team! I am wondering, why don't you take advantage of Cache control headers when processing requests for user's profiles?
For example, a url of profile (which does not require api key or any type of authentication and can be used by anyone) http://api.twitter.com/1/users/show.json?user_id=52146756 It has this header: Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 So a browser or server cannot cache this, but why? It looks like you do report the Last-Modified header and even the Etag So it would be much more efficient if you would just reply with a 304 Not modified header if request contains the If-Modified-Since value Do you support conditional requests with If-Modified-Since and with If- None-Match headers?
